search_all_codebases

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Mentions 'high-speed' and 'global token limit' but provides no information on idempotency, side effects, authentication needs, or error behavior. With no annotations, the description fails to disclose critical behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at one sentence, no filler words. However, it lacks structure such as bullet points or distinct sections that could improve readability for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters with no descriptions and an output schema present, the description only provides a high-level operation name. It omits use-case context, parameter semantics, and result expectations, leaving significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not define any parameter. 'token_budget' and 'limit_per_repo' are left unexplained despite being critical for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Uses specific verb 'executes a cross-query' and resource 'all indexed tables', clearly distinguishing it from sibling 'search_codebase' that likely targets a single repository. The scope is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'search_codebase'. The description implies it covers all indexed tables, but lacks when-not-to-use or context for selecting among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.