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 agent knows this is a safe, non-mutating operation. The description adds the scoping constraint (market-wide, date-range) but does not disclose return format, pagination, or behavior on empty results. With annotations covering safety, a 3 is appropriate.

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?

Three sentences with no redundancy. The core purpose is front-loaded, and the alternative-tool mention is placed at the end. Every sentence earns its place; no fluff.

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 complete for an agent to decide when to call it and what it does. It lacks explicit return format, but since there is no output schema and the tool is a ranking, the expected output is implied. The mention of alternatives covers routing. Given the complexity (5 params, but schema covers them), this is adequate.

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 every parameter has a detailed explanation (e.g., party_role explains plaintiff vs defendant, date formats are given). The description adds minimal additional parameter meaning beyond restating the date-range and ranking intent. Baseline 3 is correct when the schema already does the heavy lifting.

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 clearly states the verb 'Ranks' and the resource 'TTAB oppositions (or cancellations)' across the whole Board. It explicitly names two sibling tools (get_owner_ttab_stats, get_ttab_proceeding_details) to distinguish its scope, 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 provides clear context: answers market-wide ranking questions over a date range, and explicitly mentions alternatives for owner-specific and proceeding-specific data. However, it does not explicitly state when NOT to use this tool (e.g., if a single owner's stats are needed), though the alternatives imply that. Slight gap in explicit exclusions.

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