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 fully covered. The description adds useful context: it names the data source (USPTO Open Data Portal) and the return fields, and notes that query combines with structured filters via AND. It does not disclose pagination behavior or rate limits, but with annotations covering the safety profile, 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?

The description is a single dense paragraph that front-loads the core purpose, then lists return fields and filters in a logical order. Every sentence earns its place: purpose, data elements, filter list, data source. No filler or redundancy.

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 search tool with 100% schema coverage and no output schema, the description covers the essential context: what it searches, what it returns, how filters combine, and the data source. It does not explain pagination semantics beyond the schema's offset/limit descriptions, but that is a minor gap given the schema already documents those parameters.

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 8 parameters thoroughly. The description adds marginal value by grouping filters into categories (free-text query, patent_number, party, trial_type, status) and explaining the AND combination, but it does not add meaning beyond what the schema provides. Baseline 3 is correct.

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 opens with a specific verb ('Search') and a precise resource ('USPTO PTAB trial proceedings'), then enumerates the exact data elements returned (trial number, type, status, challenged patent, petitioner, patent owner, key dates). It also names the four trial types (IPR, PGR, CBM, DER), which distinguishes it from sibling tools like ptab_search_decisions and ptab_search_documents that target different PTAB record types.

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 clearly states what this tool searches (proceedings) and lists all filter dimensions, which implies when it should be used. It does not explicitly name sibling alternatives or state when NOT to use it (e.g., 'for decisions use ptab_search_decisions'), but the sibling names and the description's focus on proceedings provide adequate context for an agent to select it.

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