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

Annotations declare readOnlyHint=false and openWorldHint=true, yet the description says nothing about side effects, auth requirements, quotas, or what 'replaceByRelated' fallback behavior does to the result set. For a tool whose name implies a pure read, the false readOnlyHint is unexplained and the description leaves the agent with no behavioral context at all.

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?

It is short, but short by omission rather than by efficiency: a single sentence that merely restates the title. There is no front-loaded purpose, scope, or usage signal to anchor the agent.

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 an ambiguous 'claim data' payload, the description should clarify the response shape (claim text vs. claim metadata) and the fallback semantics of replaceByRelated. It does neither, leaving the agent unable to predict what comes back from a three-parameter patent lookup.

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 three parameters (patentId, patentNumber, replaceByRelated) are documented in the schema with separators and limits. The description contributes no additional meaning about their interaction – e.g. whether patentId and patentNumber are mutually exclusive or can be combined – 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?

The description is essentially the title repeated verbatim ('Patent Intelligence ZY: claim Data API'), a tautology rather than a statement of what the tool does. A reader can infer it fetches patent claim data from the name, but the description adds nothing – it does not say whether it returns claim text, claim counts, or claim scope, and it never distinguishes itself from siblings like nexscope_data_zy_claim_data_translated or nexscope_patent_claims.

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 guidance on when to use this tool, no prerequisites, and no mention of the closely related alternatives (the translated variant, the generic patent_claims tool, or nexscope_data_zy_query_search_patent for discovery). An agent has no basis in the description for choosing among them.

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