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

Annotations already establish this as a read-only, idempotent, non-destructive call. The description adds valuable behavioral context beyond annotations: it is sourced live from USPTO TTABVUE, returns the complete prosecution history, and includes every docket entry with dates and due dates. It does not disclose potential edge behaviors like missing-proceeding errors, but the annotation coverage lowers that burden.

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 description is dense but well-organized, leading with the core action and resource before listing output details and example questions. Every sentence contributes either the scope, the returned content, or the use cases. It is longer than strictly necessary but not padded.

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?

Because there is no output schema, the description carries the burden of explaining return values, and it does so thoroughly: type, status, dates, attorney, parties, correspondence addresses, pleaded marks, and full prosecution history. Minor gaps such as error behavior and result sizing are not critical for a single-proceeding lookup that is already well scoped.

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 the baseline applies: the schema already fully documents proceeding_number and the type disambiguation between EXT and EXA. The description adds no parameter-level detail beyond mentioning proceeding types and numbers in example questions, so it is adequate but not compensatory.

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 states a specific verb ('Returns') and a specific resource ('one USPTO TTAB proceeding in full'), and enumerates the exact contents. It also gives concrete example questions that clarify what the tool is for, clearly differentiating it from the sibling search and party-history tools.

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 example questions ('what happened in TTAB proceeding 91308065', 'is this opposition still pending', 'what is the answer deadline', 'which marks were pleaded') provide clear context for when to use the tool. However, it does not explicitly mention alternatives like ttab_search or ttab_party_history or state when not to use it, so it stops short of full routing guidance.

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