research.deep_compare

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

No annotations, so the description carries full burden. It mentions returning structured metrics and quality signals, but gives no detail on cost, latency, the 5-repo cap, or how deep 'deep' actually is. For an unannotated research tool, this is thin.

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?

Two compact sentences, purpose front-loaded. No redundancy, though it is arguably too short for the ambiguity it needs to resolve.

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?

A multi-repo research tool with no annotations, no output schema, and 0% schema coverage whose description addresses none of the parameter or behavioral gaps. The agent is left under-informed on inputs, limits, and semantics.

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 mentions zero parameters. The agent gets no clue what concept or repos should contain, how language interacts, or that repos is capped at 5.

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?

States the tool compares implementations across repos, which is a clear verb+resource. But it does not distinguish itself from siblings like github.compare or genius.find_best, leaving the agent to guess which comparison tool applies.

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 when-to-use or when-not-to-use guidance. With multiple sibling comparison tools (github.compare, genius.find_best), the description gives no signal for choosing this one.

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