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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuinely useful context beyond them: the response shape (outcome-count summary first, then records), the fields each record carries, and the upstream source (USPTO ODP). It stops short of mentioning rate limits or auth requirements inline, but the _apiKey parameter covers that.

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?

A single dense paragraph, front-loaded with the core purpose and the key disambiguation, then the return shape, then filters, then source. Every sentence carries routing or behavioral information; only the filter enumeration borders on redundant given the schema.

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?

With no output schema and nine parameters, the description must carry the return-value burden itself, and it does: it explains the outcome-count summary and enumerates the record fields. Combined with the schema's parameter docs and the annotation safety profile, an agent has everything needed 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 description coverage is 100%, so the schema already documents all nine parameters, including format and defaults. The description's filter sentence largely restates the schema (appeal_number, application_number, query, date range) and adds only marginal clarification, so the baseline 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?

States a specific verb (search) and resource (USPTO ex parte Appeals decisions), then disambiguates from the closest lookalike by declaring it a SEPARATE docket from AIA trials (IPR/PGR/CBM/derivation). The appeal-number format example ('2024-001234' vs 'IPR2024-00001') lets an agent route correctly without opening any schema.

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?

Clearly tells the agent when this tool applies (ex parte appeal decisions) and, crucially, when it does NOT (AIA trial numbers). It doesn't name a specific sibling tool to use instead, but the docket-type discriminator is strong enough to route correctly among ptab_search_* tools.

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