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 safety profile is covered. The description adds genuine context beyond that: it discloses that results are 'Sourced live from USPTO TTABVUE' (freshness) and details the exact result fields each proceeding carries (board number, type, filing date, both sides with marks and serial/registration numbers). No contradiction with annotations.

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?

Purpose is front-loaded in the first sentence, followed by concrete example questions and result format. Slightly verbose but every sentence earns its place; no filler or repetition of schema content.

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 tool with 10 optional parameters and no output schema, the description covers the main use cases, enumerates result contents, and notes the live data source. The parameter semantics are fully delegated to a complete schema, so nothing critical is missing for an agent to call it correctly.

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 coverage is 100%, so the input schema fully documents all 10 parameters including enums and defaults. The description names the search dimensions that map to the parameters but adds little beyond what the schema already provides — a marginal value-add consistent with the baseline 3 for fully-covered schemas.

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?

States a specific verb (Searches), a precise resource (TTAB proceedings), enumerates the proceeding types, and names all search dimensions (party name, mark text, correspondent law firm, application/registration number). Example questions make the intent unmistakable, and it differentiates from siblings like ttab_proceeding and ttab_party_history by covering the search-across-proceedings scope.

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 ('is anyone opposing this trademark', 'who has petitioned to cancel this registration') imply when to use it, but the description never explicitly states when not to use it or names the sibling alternatives ttab_proceeding or ttab_party_history for retrieving a single proceeding's details or a party's history. Usage is clear by inference, not by explicit routing.

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