github_search

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds beyond that by explaining the days parameter's behavior (filters by created_at) and its use as a trending substitute. This is valuable context not captured in annotations.

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 three sentences with clear structure: purpose, usage conditions, and parameter detail. No extraneous information, and key points are front-loaded.

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 has 6 parameters, an output schema (mitigating need to describe return), and rich annotations, the description is mostly complete. It explains key parameters and usage guidance but misses the language and max_results parameters. Overall, it provides sufficient context for effective use.

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%, so the description must explain parameters. It covers query (implied), days (behavior explained), and sort (default mentioned). However, language, max_results, and response_format are not described. Some parameters lack explanation, so it's partially adequate.

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 repositories by keyword via the official Search API' and distinguishes the tool from its sibling github_trending by specifying when to use each. This provides a specific verb and resource, making purpose unambiguous.

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?

Explicit conditions are given: 'USE THIS WHEN: user has a specific topic' and 'USE github_trending INSTEAD WHEN: no specific topic, just browsing.' Additionally, advice on pairing days with sort=stars is provided, giving clear decision context.

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