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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description contributes nothing further — no indication of what the returned description contains, whether absence of a patent returns empty or errors, or how the replaceByRelated fallback behaves at runtime.

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?

One short sentence with no waste, but it is under-specification rather than conciseness. Nothing is front-loaded because nothing informative is present.

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 patent full-text retrieval tool with no output schema and no annotations covering content shape, the definition should at least say what the payload is. The schema covers inputs well, but the description leaves the agent without any sense of the returned data.

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%, with all three parameters (patentId, patentNumber, replaceByRelated) fully documented including precedence and limits. The description adds no parameter meaning, 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?

"Patent Intelligence ZY: description Data API" only restates the title and adds no verb or resource framing beyond the name itself. An agent can vaguely infer it returns patent description text, but nothing distinguishes it from nexscope_data_zy_description_data_translated or nexscope_patent_description_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 prerequisites, and no mention of any sibling alternative such as the translated variant. The agent must guess from the name alone whether to call this or its near-duplicate.

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