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

The description adds value beyond the annotations by specifying the exact fields returned (titles, IDs, inventors, assignees, filing dates, abstracts). It does not contradict the readOnlyHint or openWorldHint, and it provides useful context about output without delving into rate limits or pagination, which is acceptable given 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 a single, front-loaded sentence that immediately states the action and resource, then lists the return fields with no filler. Every word contributes to understanding the tool's purpose and output.

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 read-only search tool with fully documented parameters and annotations covering safety, the description is sufficient. It explains what the tool returns and the domain, and the schema covers parameter usage. It does not mention potential pagination or result limits, but these are not critical for a simple search tool.

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%, so all eight parameters are already documented in the input schema. The description does not add any additional meaning or examples for parameters beyond what the schema provides, so it does not go above the baseline of 3.

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 a specific verb ('Search'), a specific resource ('Google Patents'), and the scope ('patent documents and scholarly articles'). It also lists the return fields (titles, IDs, inventors, assignees, filing dates, abstracts), distinguishing it from general web search tools like google_search_light and from google_scholar by the patent focus.

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 implies usage for patent searches and scholarly articles but does not explicitly compare to sibling tools like google_scholar or explain when to choose this over them. No exclusions or alternative recommendations are provided, so the guidance is only implied by the resource name and description.

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