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

Annotations are all false (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), so the description carries the burden. It discloses two important behaviors: it is asynchronous for authenticated users and returns a processing handle. These go beyond annotations and are useful for an agent to know. However, it does not explicitly state whether the operation is read-only or has side effects, though 'analyze' implies safety.

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 sentences with zero filler. The core purpose is front-loaded, and the async behavior and handle are clearly stated. Every sentence 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?

With no output schema, the description explains the immediate return (a processing handle) but does not describe the final result's format. It does describe the scope of the analysis (timeline, examiner patterns, etc.), which gives a good sense of what will be produced. It also mentions the authentication requirement and async nature, which are essential for correct invocation. Minor gap: no mention of how to retrieve the result once ready, but that may be covered by another tool.

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?

There is only one parameter, serial_number, and the schema description covers it as 'USPTO serial number' (100% coverage). The description adds no further meaning about the parameter, so it does not exceed the schema's baseline. Per the rubric, a baseline of 3 is appropriate when schema coverage is high and the description does not add parameter-specific detail.

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 analyzes the full prosecution history of a trademark, listing specific components (narrative timeline, office actions, responses, examiner decisions, status, examiner-behavior patterns). This is a specific verb+resource and distinguishes it from siblings like get_prosecution_timeline (timeline only) and get_mark_prosecution_summary (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 mentions that it is for authenticated users and launches asynchronously, which is a usage condition, but it does not provide explicit guidance on when to use this tool versus alternatives such as get_prosecution_timeline or get_mark_prosecution_summary. It implies this is a deeper analysis but never states exclusions or the alternative use cases.

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