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

Annotations declare readOnlyHint=true and openWorldHint=true, covering the safety and external-interaction profile. The description adds only the field scope (inventor/assignee). It does not disclose rate limits, auth requirements, or how suggestions are generated, so it adds limited behavioral context beyond annotations.

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?

Single sentence, front-loaded with the core action and resource, with zero wasted words. It is appropriately sized for a simple autocomplete tool.

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?

An output schema exists, so return values need not be explained. The description plus the rich schema (100% coverage) and annotations are sufficient for correct invocation; only minor context like suggestion ordering or freshness is missing.

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 100%, with both 'field' (enum-like allowed values) and 'value' fully documented. The description names inventor and assignee but adds no syntax, format, or input constraints beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb (Autocomplete) and resource (inventor or assignee name) for Google Patents search, which is clear and distinguishes it from the sibling googlepatents_search tool. It does not explicitly name alternatives, but the autocomplete scope is evident.

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?

The phrase 'for Google Patents search' implies the tool is used to build search queries, but it does not state when to use it versus googlepatents_search or any other sibling. No explicit when-not or alternative guidance is provided.

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