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

Beyond the annotations (readOnlyHint, non-destructive), the description discloses significant behavioral traits: asynchronous execution, typical duration ('usually done in under a minute'), the return of a processing handle, and the instruction to tell the user it is running. This adds value well beyond the annotation metadata.

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 three sentences long and front-loaded with purpose. Each sentence delivers essential information: the scope of analysis, the async flow and timing, and the user-facing instruction. No wasted words.

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?

Despite having no output schema, the description thoroughly covers the workflow: what it does, how it launches asynchronously, what it returns (a processing handle), and the required follow-up via get_prosecution_history_status. It also includes the user-facing instruction to keep the user informed.

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 fully describes the only parameter (serial_number) as 'USPTO serial number' with 100% coverage. The description adds no further parameter-level details, 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 uses a specific verb ('Analyze') and resource ('full prosecution history of a trademark'), listing concrete elements like narrative timeline of office actions, responses, examiner decisions, and examiner-behavior patterns. This clearly distinguishes it from sibling tools such as get_prosecution_timeline or get_mark_prosecution_summary.

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 provides clear context: it requires authentication, launches asynchronously, and directs the user to call get_prosecution_history_status to fetch the result. However, it does not explicitly compare with alternative tools or state 'when not to use', so it lacks explicit exclusions.

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