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

No annotations provided, so the description carries the burden. It discloses key traits: deterministic computation in code (not model-estimated), 'representative sample' (implying not exhaustive), and US-only coverage via PatentsView/ODP. It does not specify rate limits, return shape, or sample size, but core behavioral aspects are covered.

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 the core purpose, followed by a clarification of computation method and coverage. No wasted words; every sentence adds value.

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 tool with one parameter and no output schema, the description should ideally explain the return values (even if narrative) or clarify the parameter format. It covers output types but not their structure or the single input's expected format. Adequate but with clear gaps for an agent to call it correctly.

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 should compensate. It does not explain the single parameter 'technology_area' (e.g., expected format like 'semiconductor' or CPC code). With only one parameter, the schema provides type and length, but the description adds no semantic meaning. Baseline 3 for low coverage with no param info is appropriate.

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 uses a specific verb ('Aggregate statistics') and resource (US patents matching a technology area), and lists the exact outputs (top assignees, filing-year trend, top CPC classes) plus a narrative. This clearly distinguishes it from sibling tools like get_patent_detail or search_prior_art.

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?

Usage is implied by 'matching a technology area', but there is no explicit when-to-use vs alternatives (e.g., vs search_prior_art) or when-not-to-use. The description gives a general context but lacks exclusions or guidance on selecting this tool over others.

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