search_code

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the search action and parameter semantics, but does not mention auth requirements, rate limits, behavior for private repos, pagination, or error handling. This is a minimal behavioral description beyond the tool name.

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?

The description is extremely concise: one clear sentence and a compact Args list. Every line adds value and there is no redundant or filler content.

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 the tool's simplicity, the output schema covers return values, and all parameters are explained. However, without annotations, critical context such as authentication needs or rate limits is missing. The description is largely complete for a basic search tool but lacks some safety/contextual guidance.

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?

With 0% schema description coverage, the description compensates by explaining every parameter: keyword as 'text to search for,' language as an optional filter, owner as a GitHub user/org scoping, and limit as maximum results. These semantics add meaningful value over the bare schema property names.

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?

The description clearly states 'Search GitHub code for a keyword,' which is a specific verb+resource combination. It distinguishes from siblings like search_repository by targeting 'code' rather than repositories, though it doesn't explicitly mention these alternatives.

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?

The description implies usage for searching code snippets via the phrase 'Search GitHub code,' but it provides no explicit guidance on when to use this tool versus alternatives such as search_repository. No exclusions or contextual triggers are mentioned.

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