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

Annotations only supply readOnlyHint=false and openWorldHint=true; the description adds nothing about the external patent database being queried, latency, partial-failure behavior on a 100-ID batch, or what a citation record contains. Note the mild tension between 'Returns ... details' (implying a pure read) and readOnlyHint=false, though since the description never affirms a mutation this reads as an under-specified annotation rather than an outright contradiction.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity stems partly from omitting anything beyond the bare action.

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?

With no output schema and a heavily populated sibling space of citation tools, the description needs to say what a 'forward citation detail' record contains and how this differs from nexscope_patent_cited_by. Neither is covered, so an agent cannot confidently choose this tool over its lookalikes.

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 coverage is 100%, so both patentId and patentNumber are already documented including the comma-separated 100-item/60,000-character limits and the precedence rule. The description's 'up to 100 patents' restates the schema rather than adding 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?

States a specific verb and resource: 'Returns forward citation details' for 'patents'. That is clear enough for an agent to know what it retrieves, but it does nothing to separate itself from the near-identical siblings nexscope_patent_cited_by and nexscope_data_zy_patent_forward_citation, which appear to cover the same ground.

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 named alternative despite two sibling tools with essentially overlapping names. The only usage-adjacent information, the 100-patent batch cap, is already in the schema.

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