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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful context: it invokes an external API, explains the optional API key (sent only in X-Api-Key header, never logged), and indicates results are sorted by most recent. No contradiction with annotations. The additional source and pricing details go beyond the structured metadata.

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 a single dense paragraph of about 70 words, front-loaded with the core purpose and followed by essential details (data fields, source, pricing). Every sentence carries useful information with no filler or redundancy.

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?

Given there is no output schema, the description compensates by listing the exact data fields returned (patent id, title, grant date, assignee, Google Patents link) and the sorting order. It also explains the two data sources and pricing. This is nearly complete for a monitoring tool, though it omits details like pagination limits or error handling, which are not critical for initial selection.

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%, and each parameter has a clear description (e.g., limit, queries, sinceDays, maxConcurrency, patentsviewApiKey). The description reinforces the API key behavior but does not add significant new parameter-level meaning beyond the schema. Baseline 3 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 clearly states the tool's function: 'Watch keywords or technologies for newly granted US patents.' It specifies the resource (US patents), the action (monitoring), and the output (patent id, title, grant date, assignee, Google Patents link). This distinguishes it from sibling tools like funding-alert or layoff-tracker, which serve different monitoring domains.

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 provides context for when to use the tool and even guides on source selection: 'Bring your own free PatentsView API key' for the official USPTO-backed source versus 'keyless Google Patents source' for worldwide coverage. It does not explicitly name alternatives or exclusions, but the patent-specific purpose and source guidance make usage clear enough.

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