uspto_application_documents

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 description does not need to restate the safety profile. It adds the filtering behaviors, but does not describe pagination, return shape, or whether it returns document metadata versus full content. No contradiction exists between description and 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?

The description is two concise sentences with the primary purpose front-loaded and filter capability stated in the second sentence. There is no filler, repetition, or unnecessary detail; every phrase earns its place.

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?

Given the tool's simplicity — one required application_number parameter and three optional filters — the description plus fully described schema are enough for an agent to invoke it correctly. The description does not mention return values or pagination, but annotations already cover the read-only and idempotent nature, and the listing semantics are clear.

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?

The input schema has 100% parameter description coverage, including a comma-separated example for document_codes and date format hints for date_from and date_to. The description only summarizes these filters at a high level, adding no new format or meaning beyond the schema, so the baseline score 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 opens with a specific verb and object: 'List documents filed in a patent application,' and it gives concrete examples of what those documents are (office actions, amendments, drawings). This makes it clear the tool returns documents associated with an application, which differentiates it from the application-detail, transaction, and assignment siblings, though no sibling is explicitly named.

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 implies the intended use — retrieving patent application documents and filtering them by code or date — but it does not explicitly state when to use this tool over related siblings such as uspto_application_transactions or uspto_application_details. The usage signal is present but left to inference rather than stated.

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