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

Annotations only declare readOnlyHint=false and openWorldHint=true, which for a patent citation lookup is arguably mis-set, and the description adds nothing about whether the call is a read, what it returns, or any limits. The description carries no behavioral information whatsoever beyond the label.

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?

The single sentence is short but empty; it is under-specification rather than conciseness. Nothing is front-loaded because there is nothing to load beyond the tool's own name repeated.

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?

Two optional parameters and no output schema mean the description must carry the burden of explaining what a citation query returns and how it differs from sibling citation tools, and it does neither. An agent cannot call this correctly on the description alone.

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 both patentId and patentNumber are fully documented in the schema, including comma separation, the 100-item cap, and the priority rule. Per the baseline rule, a 3 applies even though the description itself contributes no parameter meaning.

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 a restatement of the title: 'Patent Intelligence ZY: patent Cited API.' It never says what the tool actually returns (citing patents? cited patents? citation counts?) or which identifiers qualify. With siblings like nexscope_data_zy_patent_forward_citation, nexscope_patent_cited_by, and nexscope_data_zy_patent_family in the same namespace, this ambiguity is costly.

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 prerequisite or exclusion, and no mention of how this differs from the near-identical citation siblings. An agent has no basis for choosing this tool over nexscope_patent_cited_by or nexscope_data_zy_patent_forward_citation.

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