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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds nothing beyond repeating the name — no cost, latency, auth, or side-effect context. With no annotations-style safety context and a lone title fragment, an agent has zero basis for knowing what happens on invocation or what the response contains.

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 it is a single title fragment with no front-loaded purpose statement and no information payload; brevity here reflects under-specification rather than economy.

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 4-parameter patent-data tool with no output schema and only two minimal annotations, the description should explain what data comes back, acceptable input combinations, and translation behavior. It supplies none of this, leaving an agent unable to invoke it correctly with confidence.

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 fully documents lang, patentId, patentNumber, and replaceByRelated including defaults and limits. The description contributes no parameter meaning of its own, so the baseline 3 applies — the schema, not the description, carries the semantics.

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 title/name ("Patent Intelligence ZY: abstract Data Translated API") with no verb describing what the tool actually does. It hints at a domain (translated patent abstracts) but never says whether it retrieves, translates, or resolves abstracts, nor does it distinguish it from siblings such as nexscope_data_zy_abstract_image, nexscope_data_zy_claim_data_translated, or nexscope_patent_title_abstract_translation.

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 prerequisites, and no mention of alternative sibling tools. An agent cannot tell from the description alone whether this should be preferred over nexscope_data_zy_abstract_image or the non-ZY nexscope_patent_title_abstract_translation variant.

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