Get Patent Global Citation Class

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

The readOnlyHint annotation already establishes that this is a safe read, and the description adds nothing beyond that: no return shape, no mention of whether the class data may be empty for some publications, and no note on rate limits or lookup failure behavior. The description carries no value over the annotation.

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 filler and the verb front-loaded. It is efficiently sized, though that brevity comes at the cost of substance rather than being a model of tight expression.

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 and only a readOnly annotation, the description is the sole channel for explaining what 'global citation class' data an agent receives and in what form. It leaves that entirely unaddressed, so an agent cannot predict the response or confirm this is the right sibling.

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% and the single parameter is documented with a concrete format example ('JP.12345678.A'), so the schema does the heavy lifting. The description contributes no additional parameter meaning, which matches the baseline 3 for fully-covered schemas.

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 largely restates the tool name: 'Fetch patent global citation class information' is a verbatim rewording of 'Get Patent Global Citation Class'. It never explains what a 'citation class' actually is or how this differs from siblings like get_patent_citations or get_patent_global_doc_list, so an agent cannot distinguish the resource on substance.

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 statement of when to use this tool, when not to, or which sibling to prefer for adjacent needs (e.g. general citations vs. this class-specific call). The only implied guidance is the single required applicationNumber, which is insufficient routing information.

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