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

The description frames the tool as returning data, implying a read-only lookup, while the annotations declare readOnlyHint=false. This conflicts with the stated behavior, and no additional behavioral context such as permissions or response format is provided.

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 front-loaded, efficient, and contains no filler or repetition. It communicates the core operation and batch size immediately.

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?

There is no output schema, so the description should more fully characterize the returned counts and citing records. It also omits usage context and leaves the annotation discrepancy unaddressed, though the basic scope is present.

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%, and the schema already documents patentId, patentNumber, their comma-separated batch syntax, and precedence rules. The description adds only the general "up to 100 patents" limit, without clarifying parameter differences.

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 uses a specific verb and resource: "Returns cited-by counts and citing patent records," and states the batch limit of 100 patents. It does not distinguish this from sibling citation tools such as nexscope_patent_references or nexscope_data_zy_patent_forward_citation.

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?

It mentions the 100-patent batch limit but gives no guidance on when to use this tool versus related citation or patent-detail siblings. An agent must infer its role from the name alone.

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