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

No annotations provided; description covers retrieval method, sorting, and parent bundle reference. However, lacks details on authentication, rate limits, or any destructive traits. Given no annotations, this is adequate but not rich.

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 sentences, front-loaded with purpose, second adds crucial context. No redundant or vague wording.

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?

For a search tool with 3 params and no output schema, the description covers key aspects: what is searched, how results are ordered, and how to act on them. Minor omission: no mention of pagination or error handling, but adequate for typical 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 has 100% coverage for parameter descriptions. Description adds value by explaining result sorting (fidelity score) and how to use results with download_bundle, going beyond what schema provides.

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?

Clearly states the tool searches extracted claims using hybrid vector + full-text retrieval, returns top claims sorted by fidelity score. It distinguishes from sibling 'search_bundles' which searches bundles, not claims.

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?

Provides context for use: searching claims, and notes that results reference parent bundles for download. Does not explicitly state when not to use or alternative tools, but the sibling list implies differentiation.

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