Get Patent Global Document List

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered structurally. The description adds no behavioral context of its own: nothing about what the 'list' contains, whether results are paginated or bounded, or how the global scope differs from the other patent document endpoints.

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 short sentence with no wasted words, and it is front-loaded. However, it is concise by omission rather than by discipline: the brevity comes from under-specification, which leaves the definition thin rather than efficient.

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 lookup tool with no output schema, the description should at least say what the returned document list represents and how it relates to the sibling document endpoints. Neither is provided, so an agent lacks enough to call this confidently over its near-duplicates.

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?

There is one well-documented parameter with 100% schema description coverage (applicationNumber with a format example), so the schema carries the load and the baseline is 3. The description contributes no additional parameter meaning, so it cannot rise above the baseline.

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 states a verb ('Fetch') and a resource ('patent global document list'), so the basic purpose is clear. But it adds nothing beyond the title and does not distinguish this from close siblings like get_patent_global_document, get_patent_documents, or get_patent_jp_document, so an agent cannot tell which one to pick without reading schemas.

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?

No when-to-use guidance, no prerequisites, and no mention of the alternative document-listing tools in the sibling set. The agent is left to infer usage entirely from the name.

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