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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations by explaining the tool uses 'the same discovery index as the GleanMark TTAB workspace' and by warning about the real-world Oppositions-vs-Cancellations filing pattern. It does not mention rate limits or result pagination, but for a read-only search tool this is strong coverage.

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 three sentences with zero waste: it states the purpose, lists accepted inputs and filters, and routes to alternatives. The special domain warning is embedded inside the relevant parameter description rather than bloating the main text. Every clause 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?

Given the tool's moderate complexity (6 parameters, no output schema), the description covers the search scope, filter behavior, and sibling differentiation thoroughly. The main gap is the lack of any statement about the response format or result shape, which an output schema would normally fill. Still, an agent can confidently invoke this tool correctly based on the description alone.

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 67%, and the description compensates significantly. The type_filter description far exceeds the schema by explaining accepted singular forms and codes ('Cancellation'/'CAN' → Cancellations) and the real-world pattern about Monster Energy-style enforcers. The query parameter's accepted formats and the owner_contains semantics are also clarified. Only status_filter gets no additional explanation, but overall the description adds strong meaning 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 states a specific verb and resource ('Search TTAB proceedings') and explicitly lists the supported search inputs and filters. It names two sibling tools (get_ttab_proceeding_details, get_owner_ttab_enforcement) to distinguish when this tool is not the right choice, which clearly separates it from the many related TTAB 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 description explicitly tells the agent when to use this tool ('broad proceeding discovery') and when to use alternatives ('For one known case after discovery, use get_ttab_proceeding_details; for owner enforcement statistics, use get_owner_ttab_enforcement'). It also gives concrete domain-specific guidance about the cancellations filter behavior, which helps prevent misdiagnosis of results.

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