dossier

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

Discloses caching and credit costs, but no annotations exist; missing information on rate limits, errors, or authentication requirements.

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?

Every sentence adds value; starts with purpose, lists returns, explains costs, and positions tool. No wasted text.

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?

Comprehensively lists returned data despite no output schema; lacks mention of error handling or detailed format, but sufficient for a fetch tool.

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?

Adds value beyond schema by explaining input normalization ('Accept loose input...'), which standard schema description does not convey.

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?

Description clearly states 'Fetch a comprehensive intelligence dossier for a patent' and lists all returned data types, distinguishing it from sibling tools like 'citations' or 'family'.

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 clear cost and caching behavior, and identifies as 'headline tool' where most workflows start, but does not explicitly mention when to avoid using it or alternatives.

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