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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context about the market-wide aggregation scope and the date-window ranking behavior. It does not describe return format or pagination, but that is a minor gap given the read-only nature.

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 compact: three sentences with no filler. It front-loads the core purpose, then provides usage criteria, exclusions, and an invocation hint. Every sentence 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 read-only ranking tool with a fully documented schema and clear sibling differentiation, the description is complete. It covers what the tool does, when to use it, when not to use it, and how to pass the date range. No critical information is missing for selection or invocation.

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%, with each parameter already fully explained including date format examples and enum meanings. The description adds the useful instruction to pass the exact calendar range, but overall it does not need to compensate for parameter documentation gaps.

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 ('Rank') and names the exact resource: parties that filed TTAB oppositions (or cancellations) Board-wide. It explicitly distinguishes itself from sibling tools like get_owner_ttab_stats and get_ttab_proceeding_details by stating it is the only tool that ranks filers market-wide.

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?

It gives clear when-to-use guidance with a concrete example question ('which party filed the most oppositions in April 2026?') and explicit negative routing ('Do NOT substitute get_owner_ttab_stats... or get_ttab_proceeding_details'). It also tells the agent to pass the exact calendar range the user implied.

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