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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results include top-assignee/inventor/classification breakdowns, a useful behavioral trait beyond annotations, but says nothing about pagination, result caps, or query syntax.

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?

A single front-loaded sentence that packs the verb, resource, facet list, and output note with no filler. Slightly dense but every clause carries information.

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 described. For a 13-parameter tool with 0% schema description coverage and no enums, the description is adequate about filters but incomplete on pagination/sort semantics and accepted value formats.

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 carries the burden and does map most filters (keyword, inventor, assignee, patent office/country, status, type, language, date) to parameters. However it leaves num, page, sort, and date_field unaddressed and gives no value formats (e.g. date format, valid type/status values).

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?

States a specific verb (Search) and resource (Google Patents) and enumerates the searchable facets, so the agent knows exactly what the tool retrieves. It does not explicitly differentiate itself from siblings like googlepatents_recent or googlepatents_classification, so it falls short of a 5.

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?

There is no guidance on when to prefer this tool over googlepatents_recent, googlepatents_detail, googlepatents_classification, or googlepatents_suggest. The description lists what can be searched but never states conditions, exclusions, or alternatives.

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