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

Annotations cover read-only and open-world status, and the description adds real behavioral content beyond them: results are the records the offices actually returned (no synthesis), each carries a Google Patents link, and ranking is lexical word-overlap rather than semantic. The 'not legal advice' disclaimer sets usage expectations. Minor gap: no note on result ordering confidence or rate limits.

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?

Front-loaded with the core action, then the ranking caveat, then the disclaimers. Short and free of filler, though the two trailing disclaimer sentences could be merged into one without losing content.

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?

With no output schema, the description carries the return-value burden and does so adequately: closest returned records with Google Patents links, plus an explicit note on how they are ranked. It omits pagination/refinement behavior and guidance for when the search returns nothing, which is a modest gap for a 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%, with min/max bounds for both 'idea' (20-4000 chars, plain language) and 'limit' (1-25) already documented in the schema. The description adds no meaning beyond 'idea description', 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?

Concrete verb+resource: it converts an idea description into a public-patent search and returns the closest matching records plus Google Patents links. The 'idea description' input differentiates it from keyword-style siblings like search_patents, but no sibling is named explicitly, so differentiation is left to inference.

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 clarifies what the tool is NOT (not a patentability opinion, not legal advice) but gives no positive when-to-use guidance and never contrasts it with find_patent_citations, get_patent, or search_patents. An agent gets no routing rule for choosing this over the keyword-search sibling.

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