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

Goes well beyond annotations: it discloses that existing relationships are retained so bad links cannot be removed, that text/PDFs/legal status/classification are left unchanged, that competitor records are unsupported, that a null links result means the update did not finish, and that refreshes cost credits and are refused when credits are exhausted. All of this is consistent with destructiveHint=false and idempotentHint=true.

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?

Dense but well front-loaded: purpose first, then when-to-use, then constraints, then result semantics. A few sentences are long and could be split, but no sentence is filler and each carries operational information.

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?

Covers what the tool does, when to use it, what stays unchanged, cost/refusal behavior, and result shape, including the important caveat that no family-member list is returned and results do not establish complete coverage. Despite an output schema existing, the added clarification about results is not redundant noise.

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 single parameter is already documented, so the schema does most of the work. The description still adds meaning by narrowing the valid input to an own patent record and stating competitor records are not supported, preventing a wrong-id call.

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 ('Updates family grouping for one saved own patent') plus the data sources it draws on (public patent information, related own patents already saved). It is clearly distinguishable from siblings like import_patent and search_public_patents.

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?

Gives explicit triggers ('apparent missing relationship, an unfinished family update, or a requested check against newer public information') and exclusions ('Imports already attempt family grouping automatically; routine refresh after import is unnecessary'). It also names alternatives and their limits: 'Repeating import_patent only retrieves its saved outcome' and related publications must be imported separately first.

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