uspto_application_documents

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

The readOnlyHint annotation already declares this as a safe read operation, and the description's use of 'List' is consistent (no contradiction). The description adds modest context by enumerating document types and filters, but it does not disclose pagination, return format, or any other behavioral traits beyond what annotations and the description already imply.

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, front-loaded sentence that states the primary function first and then lists filters. Every phrase earns its place, and there is no redundant information.

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 list tool with one required parameter and no output schema, the description is largely complete: it conveys the resource, scope, and filtering capabilities. It does not mention return format or pagination, but given the simplicity and the readOnly annotation, it is sufficient without being verbose.

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 schema descriptions already cover all parameters (100% coverage), so the baseline is 3. The description adds value by explicitly mentioning 'filter by document code or date range', which clarifies how document_codes and date_from/date_to are intended to be used. This goes slightly beyond the schema's individual descriptions.

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 uses the specific verb 'List' and clearly identifies the resource: documents filed in a patent application. It also provides examples of document types (office actions, amendments, drawings) and states the filtering options, making it easy to distinguish from sibling tools like uspto_application_details or uspto_application_transactions.

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 when to use the tool: when you need to list documents in an application, with filtering by document code or date range. However, it does not explicitly name any alternative tools or state when not to use it, so the guidance is implied rather than explicit.

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