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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description's one genuine addition is the '1 credit' cost disclosure, but it says nothing about pagination limits, rate limiting, or result volume.

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?

Two fragments, zero filler, and the core purpose leads ahead of the cost note. It is efficient, though the extreme brevity edges toward under-specification rather than disciplined conciseness.

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 a rich annotation set and mostly documented parameters, the essentials are present, and the credit cost is a useful operational detail. Missing are result shape and behaviour notes (e.g. how country and language interact, what happens at page 10) for a four-parameter search tool with no output schema.

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 75%, with country and language explained in the schema and page bounded by min/max, so the schema carries most of the load. The description adds no parameter meaning of its own, making the baseline 3 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 gives a clear verb+resource ('Search patents'), so an agent immediately knows the domain. It does not distinguish itself from near-neighbours like scholar, news, or general search, which is the one thing missing for a top score.

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 when-to-use guidance and no named alternative; an agent must infer that this is for patent literature rather than scholarly papers (scholar) or general web results (search). The only context offered is the cost note, which does not help routing between siblings.

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