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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that - it doesn't mention the read-only nature, the multi-ID batching behavior, or the 100-record cap that governs practical use. No contradiction, but zero value added.

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 tautology - it repeats the title verbatim and earns no place. Brevity without information is under-specification, not conciseness.

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?

The tool is simple (2 optional params, no output schema, no nesting), so the schema alone almost suffices, but an agent still has no statement of what a patent-family response contains (family members, jurisdictions, priority links) or how family data relates to the sibling bibliography and citation tools. Nothing an agent needs to disambiguate the call 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 description coverage is 100%, so both patentId and patentNumber already carry full semantics including the comma-separated batch format, the 100-item limit, and the precedence rule when both are supplied. Per the rubric, baseline 3 applies when the schema does the heavy lifting; the description contributes nothing further.

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 adding a verb, an object of the operation, or any explanation of what a patent family lookup returns. An agent can infer the resource domain (patent families) only because the name already says it, not because the description explains it.

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 about when to use this tool versus the many patent siblings such as nexscope_data_zy_bibliography, nexscope_data_zy_patent_cited, or nexscope_data_patents_search. No prerequisites, no exclusions, no alternatives named.

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