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

Discloses that it returns result IDs for use with fetch, implying it is a lightweight search. With no annotations, description carries burden, but omits potential pagination or error behavior; still adequately transparent.

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 plus a parenthetical note deliver purpose, usage, and alias relationship without wasted words. Front-loaded with main action.

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 simple one-parameter search tool with no output schema, the description covers purpose, return value, and relationship to sibling. Could mention potential limits or result count, but still sufficient.

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 coverage, description compensates by explaining the 'query' parameter is for free-text search, adding meaning beyond the schema's bare type and property name.

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 VICP vaccine-injury cases by free text and returns result IDs for fetch. Differentiates from sibling search_cases by mentioning alias relationship and usage preference.

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?

Explicitly tells when to use search_cases instead (when structured filters available) and that this tool is an alias for deep-research clients. Provides clear context for tool selection.

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