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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description adds no behavioral context at all — no mention of what is retrieved, whether calls consume quota, or how failures are handled. It does not directly contradict the annotations, so no contradiction flag, but it contributes nothing beyond them.

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 the single sentence is pure duplication of the title and carries zero information. This is under-specification rather than genuine 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?

For a 3-parameter data-retrieval tool with no output schema, the description should explain what data comes back and how it differs from the translated sibling. The rich input schema partially compensates, but the agent is left without enough to select or interpret results confidently.

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 schema itself clearly documents patentId, patentNumber (including the precedence rule) and replaceByRelated. The description adds nothing about parameters, so the baseline of 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 a restatement of the tool title and name — 'Patent Intelligence ZY: description Data API' — with no verb describing what the tool actually does. It implies the tool returns patent description data, but gives no scope or distinguishing detail versus siblings like nexscope_data_zy_description_data_translated or nexscope_data_zy_claim_data.

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, no preconditions, and no reference to any alternative tool. With roughly a dozen ZY patent-data siblings, an agent has no basis for choosing this tool over the translated variant or the abstract/claim endpoints.

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