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

Annotations declare readOnlyHint=false and openWorldHint=true, an unusual profile for what reads as a data-retrieval endpoint; the description neither confirms nor contradicts this, so it adds no behavioral context. It says nothing about batching limits, cost, latency, or what happens when both identifiers are supplied beyond what the schema already states.

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 short, but the single sentence is pure redundancy with the name and title and earns no place. Conciseness here reflects under-specification rather than efficiency.

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, the description must carry the burden of explaining what family data comes back (family members, relation types, jurisdictions) and it does not. The schema covers inputs, but an agent has no basis for predicting the response shape or deciding this tool fits its need.

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 schema already documents comma separation, the 100-item limit, the 60,000-character cap, and the priority rule for patentId over patentNumber. The description contributes nothing beyond that, so the baseline of 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?

The description restates the tool name and title ("Patent Intelligence ZY: patent Family API") without a verb or any statement of what the tool actually returns. An agent can infer it relates to patent families but cannot tell whether it retrieves family members, family metadata, or legal family linkage, nor how it differs from siblings such as nexscope_patent_family_data or nexscope_data_zy_simple_bibliography.

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 exclusions, and no mention of alternatives, despite a large sibling set containing several patent-family and bibliography tools. Nothing indicates whether patentId or patentNumber should be preferred, or when to choose this over nexscope_patent_family_data.

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