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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds context about what data is returned (status, counts, dates, milestones), but does not disclose additional behavioral traits like error handling, data freshness, or limitations. This is adequate but not exceptional given the existing 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 sentences: the first states the purpose, the second lists return contents. It is front-loaded, succinct, and every phrase adds value. No redundant or verbose language.

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 parameter, no output schema), the description adequately explains what the tool does and what it returns. It lists the key return categories, which is sufficient for an agent to decide whether to use it. However, it does not mention edge cases like empty results or error behavior, which would make it more complete.

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%, with serial_number described as 'USPTO serial number.' The tool description does not add extra meaning beyond the schema, such as format requirements or examples. Since the schema already documents the parameter, the baseline 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 clearly states the tool's function: 'Get a compact prosecution summary for a trademark serial number.' It specifies the resource (trademark serial number) and the output contents (current status, document counts, dates, milestones, key event). This distinguishes it from sibling tools like get_prosecution_timeline or get_latest_office_action, which focus on specific aspects.

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 usage for a quick overview ('compact summary') but does not explicitly state when to use this tool over alternatives. No exclusions or alternative recommendations are provided, so the usage context is only implied rather than clearly guided.

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