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

It reveals crucial behavioral traits about the output structure—it explicitly states that the API returns `citations` and `enriched_citations` separately and explains the technical reason for this (lack of shared key), which is high-value context.

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 explanation is dense with information but highly efficient; every sentence adds necessary technical or scoping context, and the most important functional details are front-loaded.

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 description is highly complete, addressing the specialized nature of the USPTO data, including the unique design choice to return two distinct, unjoined datasets.

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?

With 100% schema coverage, the description excels by elaborating on the complexity of the result that those parameters enable, detailing the type of enriched data generated by USPTO.

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 purpose is highly specific: retrieving references cited in office actions. It clearly delineates the scope of the data provided (who cited, legal basis, and AI-extracted fields).

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 is a specialized tool, and its detail about returning basic vs. enriched citations inherently dictates its usage when citation-level data is required rather than full text or rejections.

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