AI-friendly, fully local, semantic code search tool for large codebases
Scoring was not performed
delegate tool has empty input schema (no properties defined) and minimal description ('Delegate execution to external systems or tools'). This violates tool definition requirements and makes it unusable for agents.
No output schemas documented for any tool. Agents cannot plan downstream calls or extract return fields without knowing structure. This forces trial-and-error usage and wastes tokens on parsing.
No error handling guidance provided. Tools do not document what errors are retryable, what the agent should do on failure, or how to distinguish user-fixable from fatal errors.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 44 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 37 | - | v1 |
Parameter descriptions for 'search' tool are present but lack format guidance. The 'exact' parameter description does not explain the difference between stemmed and exact search clearly enough for LLM decision-making.
The 'query' tool accepts a 'language' parameter but does not enumerate valid language values (rust, javascript, python, go, etc.) as an enum or constraint. LLMs may hallucinate unsupported languages.
The 'implement' tool has a 'backend' parameter with no enumerated valid values (aider, claude-code mentioned in description but not formalized). This invites hallucinated backend names.
No pagination guidance for 'search' and 'query' tools despite accepting 'max_results'. The 'search' tool mentions session-based pagination but does not document max result limits or when pagination is necessary.
No documentation of which tools are idempotent vs. state-modifying. The 'implement' tool modifies code but does not warn agents about retry implications or include a dry-run explanation.
Vague description for 'delegate' tool ('Delegate execution to external systems or tools') fails to explain what it actually does, when to use it, or what parameters it expects (schema is empty).