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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds value by enumerating the returned fields, which is especially useful given there is no output schema. It does not discuss error behavior or rate limits, but for a simple read-only lookup this is acceptable.

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?

Two compact sentences with no filler. The first sentence front-loads the action and key parameter; the second efficiently lists the return payload. Every word earns its place.

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 single-parameter, read-only lookup tool, the description is nearly complete: it states the identifier format, what the tool returns, and the read-only nature via annotations. It does not specify behavior when a patent_id is invalid or not found, but this is a minor gap for such a simple 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 coverage is 100% and the sole parameter patent_id is already documented in the schema with the same example ('10757852'). The description reinforces that the parameter is a single USPTO patent identifier but adds no new semantic detail beyond the schema.

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 ('Fetch full details') and resource ('single patent by its USPTO patent_id'), explicitly distinguished from sibling search tools. It also lists the concrete return fields (title, grant date, type, abstract, assignees, inventors, citation count), leaving no ambiguity about what this tool does.

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?

The description clearly establishes the use case: retrieving complete details for one patent when the patent_id is already known. It does not explicitly name alternatives like patent_search for discovery, but the single-patent-by-ID framing provides clear context that this is not a search or listing tool.

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