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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral details: includes stable document identifiers, working USPTO links 'when available', extraction/readability status, and types of filings. This goes beyond the schema and 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?

Two tight sentences. The first provides a clear list of what the tool returns; the second gives a direct pointer to the sibling tool. No waste, front-loaded with the primary action.

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 read-only list operation with a fully described schema, the description covers the key context: what is returned (identifiers, links, status, document types) and how to proceed to read a specific doc. No output schema exists, but the described return content suffices.

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% (both serial_number and limit are described). The description adds no new parameter-specific guidance, though it reinforces that the tool is scoped to a serial number. Baseline 3 applies because the schema already carries the parameter semantics.

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?

States specific verb (list) and resource (prosecution documents for a trademark serial number), and enumerates included content types. Also distinguishes from sibling get_prosecution_document by explicitly directing to that tool for reading a single document.

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?

Explicitly tells the agent to use get_prosecution_document for reading one selected document, clarifying the complementary relationship. However, it does not mention alternatives like get_prosecution_timeline, and lacks explicit 'when not to use' exclusions beyond the one tool.

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