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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds meaningful behavioral context: it 'reads several result pages' (indicating multi-step fetching and potential latency) and notes data is 'sourced live from USPTO TTABVUE' (implying freshness and external dependency). These traits go beyond the structured hints.

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 front-loaded with the core function and output breakdown, followed by concrete example questions that ground the purpose. It is moderately long but every sentence adds value; there is no filler or repetition. It could be tightened slightly but is well-structured.

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 profiling tool with a rich schema and annotations, the description adequately covers what is returned (counts, breakdowns, spellings, proceedings) and notes the multi-page reading behavior. It does not mention response format or pagination limits, but the schema already defines max_pages and limit. Given no output schema, the description still provides enough to decide on 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 (party, status, max_pages, limit, match_mode) already having a clear description in the schema. The description does not add any parameter-specific nuance beyond what is already in the schema, so the baseline of 3 is appropriate.

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 is highly specific: it states the tool profiles a company or person across USPTO TTAB proceedings, enumerates exact outputs (plaintiff/defendant counts, proceeding type breakdown, name spellings, proceedings list), and gives concrete example questions. This clearly distinguishes it from siblings like ttab_proceeding (detail on a specific case) and ttab_search (general search).

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 provides example questions that map to use cases (e.g., 'how often does this company oppose other trademarks'), which strongly implies when to use it. However, it does not explicitly mention alternatives or exclusions, such as 'use ttab_search for keyword-based searches' or 'use ttab_proceeding for case details'. The purpose is clear enough that a capable agent would infer the right context, but explicit contrast would be stronger.

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