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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds nothing beyond that — no indication of citation direction, result shape, or the 100-ID batch limit behavior. With annotations present the bar is lower, but zero added context is still a gap.

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 only one short sentence, so there is no padding, but this is under-specification rather than conciseness: the single sentence is a restatement of the title and conveys no actionable information.

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 citation-lookup tool in a dense patent family with no output schema, the description should at minimum disambiguate citation direction and clarify the batch semantics. It supplies neither, leaving the agent unable to predict what comes back or how this differs from siblings.

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 parameter descriptions fully document the comma-separated format, the 100-item limit, the 60,000-character cap, and the patentId-over-patentNumber precedence. Baseline 3 applies since the schema carries the semantics and the description adds none.

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 restates the title verbatim: 'Patent Intelligence ZY: patent Cited API.' It never says what the tool actually returns — whether it lists patents cited by the given patent or cited-by records. The word 'Cited' is the only semantic hint, and it is ambiguous next to siblings like nexscope_data_zy_patent_forward_citation and nexscope_patent_cited_by.

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, and no mention of the many patent siblings (bibliography, claim_data, patent_family, forward_citation, cited_by). An agent has no basis, from this text, to choose this tool over its near-duplicates.

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