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

The description describes a read-only retrieval operation ('Returns patent family identifiers and members'), but the annotations declare readOnlyHint=false, implying the tool is not read-only. This is a direct contradiction, and the description provides no additional behavioral context to resolve it.

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 description is a single efficient sentence with the verb and resource front-loaded. Every word contributes to stating what the tool returns and its batch scope.

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 simple two-parameter retrieval tool with full schema coverage and no output schema, the description is minimally adequate. However, it does not clarify what 'members' includes, how results are structured, or why this tool should be chosen over the similar sibling patent-family tool.

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 already well documented, including the precedence rule for patentId. The description adds only a redundant batch limit and no parameter semantics beyond the schema, making the baseline 3 appropriate.

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 clearly states a specific verb and resource: it returns patent family identifiers and members, with a scope of up to 100 patents. It does not explicitly differentiate itself from sibling tools such as nexscope_data_zy_patent_family, so it stops short of a 5.

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 gives a batch limit but no guidance on when to use this tool versus alternatives like nexscope_data_zy_patent_family or nexscope_patent_search. It also omits any prerequisites or input-selection advice, leaving the agent to infer usage.

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