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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description adds nothing about behavior, coverage, or result characteristics beyond echoing the title. It neither contradicts nor enriches what the annotations already state, so it contributes essentially no behavioral context.

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 one short sentence, but the sentence is pure redundancy with the name/title, so its brevity comes from under-specification rather than efficiency. Nothing is front-loaded beyond the tool's own name.

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 data-retrieval tool with no output schema, the description should clarify what a forward-citation lookup returns and how it differs from its many citation/parent siblings, but it provides none of that. What the agent would need to invoke it correctly is missing.

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 optional parameters (patentId, patentNumber) are fully documented in the schema, establishing the baseline of 3. The description adds no extra meaning about how the two identifier types interact or which to prefer.

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 tool name and title ("Patent Intelligence ZY: patent Forward Citation API"), identifying the resource as patent forward citations but adding no specific verb or scope. It does not distinguish this from closely related siblings such as nexsco_patent_cited_by or nexsco_data_zy_patent_cited.

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 guidance on when to use this tool versus alternatives, and several near-identical siblings exist (nexscope_patent_cited_by, nexsco_data_zy_patent_cited, nexsco_patent_references). The agent must infer usage entirely from the name.

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