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

Beyond the readOnlyHint annotation, it discloses 'computed live from keyless PatentsView data,' weekly updates, the optional history tier requirement, and the returned fields (score, trend, confidence, top_drivers, etc.). This gives agents useful runtime and data-source context well beyond the 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?

The description is three dense sentences: the first front-loads return semantics, the second gives call context, and the third states update cadence. Every sentence earns its place and there is no filler or redundant restating of the schema.

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?

Despite having no output schema, the description names all key return sections and covers the optional history mode plus freshness/cadence. Combined with readOnlyHint and a fully documented optional parameter, this is sufficient for an agent to select and invoke the tool without ambiguity.

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 coverage is 100% and the sole optional `days` parameter already has a detailed schema description specifying range, history behavior, and Gold tier requirement. The tool description adds no additional parameter-level semantics, so the baseline 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?

Description opens with 'Returns a 0-100 US patent grant velocity index...', providing a specific verb, resource, and metric definition. It also enumerates the output components, making the tool's purpose clear and distinct from sibling patent-related tools.

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 description explicitly states 'Call when the user asks about patent activity, USPTO grant pace, innovation output, or R&D cycles' and extends to timing patent-landscape refreshes, prosecution staffing, or competitive IP monitoring. It gives strong contextual guidance but does not mention when not to use the tool or name alternative tools.

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