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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the tool's safety profile is well covered. The description adds useful behavioral context by specifying exactly what the summary contains, which helps set expectations even without 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?

Two short sentences with the action front-loaded and the returned information presented as a tight enumeration. There is no filler, redundancy, or unnecessary background.

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 simple, single-parameter, read-only summary tool, the description covers the main output contents and the annotations cover safety. It does not address edge cases or serial-number formatting, but the schema and annotations already handle the critical structured context.

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 coverage is 100% and the single parameter is already described as a 'USPTO serial number.' The description only repeats this as 'trademark serial number' without adding format, normalization, or example guidance, so it meets the baseline but adds no extra semantic value.

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 ('Get') and identifies the resource as a 'compact prosecution summary' for a trademark serial number. It then enumerates concrete return components (current status, document counts, dates, milestones, latest key event), which distinguishes it from siblings like get_prosecution_timeline, get_latest_office_action, and get_mark_ai_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 implies usage for a quick overview via 'compact' and 'latest key event,' but it does not explicitly name alternatives or provide when-not-to-use guidance. An agent could infer the difference from get_prosecution_timeline or analyze_prosecution_history, but the route is not stated.

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