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

Annotations already establish read-only, idempotent behavior, so the description only needs to add behavioral context. It adds meaningful beyond-schema details: the source is the USPTO Open Data Portal, the tool returns specific document fields, and it describes the scope as 'every document filed in a proceeding.' This goes beyond the minimum, though it does not mention pagination or auth rate-limit behavior.

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 compact, front-loaded with the core action, then usage, then return fields, then data source. Each sentence earns its place with no wasted words or redundancies.

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, the description appropriately explains return fields. All five parameters are documented in the schema, annotations cover safety and idempotence, and the description explains the data source and primary invocation modes. It is complete enough for an agent to invoke correctly; only explicit sibling routing is missing.

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 baseline is 3. The description adds only minor reinforcement of proceeding_number and query semantics, mainly restating what the schema already documents. It does not meaningfully compensate or extend the parameter understanding beyond the schema.

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 tool's purpose: searching USPTO PTAB filings and documents within trial proceedings, with a specific list of document types. It is clear and resource-specific, but it does not explicitly distinguish itself from sibling tools like ptab_search_proceedings or ptab_search_decisions, so it misses the top score.

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 gives concrete usage guidance: pass proceeding_number to list every document in a proceeding, and/or query for free-text search, and notes the two can be combined. This is clear operational context, but it does not mention when to prefer sibling tools or state exclusions, stopping short of 5.

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