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

Annotations already establish that this is a safe, read-only, idempotent, open-world search. The description adds useful behavioral context by saying the results are final petition decisions and by listing returned fields (decision type, date, petition type, deciding office), which compensates for the lack of an output schema.

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 four tight sentences with no filler, and it is front-loaded with the core purpose. Each sentence contributes either scope, mode selection, date filtering, or return fields.

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 an eight-parameter search tool with no required parameters and no output schema, the description covers purpose, main query modes, date bounds, and return fields well. It leaves pagination and API-key handling to the schema, which is reasonable, but it could more explicitly mention limit/offset behavior or authentication requirements.

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 every parameter. The description restates the main query modes and date bounds, adding only modest meaning beyond the schema's own parameter 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 states a specific verb and resource: searching USPTO Commissioner / Office of Petitions final decisions. It is clear what the tool does, but it does not explicitly distinguish this dataset from sibling tools such as search_office_actions.

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?

It gives clear mode guidance: use application_number for one application's petition history, or use query for free-text search across decisions. It does not name alternatives or exclusions, but the usage context is explicit enough to choose between the two main access patterns.

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