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

Annotations already establish the tool as read-only and non-destructive, and the description adds non-obvious behavioral context: results are citable, include a public URL, have stable ids, and cover both live and dead USPTO applications and registrations. It does not discuss pagination or result limits, but the safety profile is already covered by 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 four short sentences, each earning its place: the first establishes the core purpose, the second defines result structure, the third gives the follow-up workflow, and the fourth states coverage scope. There is no redundant or filler content.

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?

There is no output schema, so the description partially compensates by describing the shape of each result and directing agents to fetch full records. It does not mention pagination, result limits, or ranking behavior, but for a single-parameter search tool that returns citable summaries, the description is reasonably 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 the query parameter already documented as mark, brand, or owner name with an example. The description restates similar semantics but adds no meaningful parameter-level detail beyond what the schema provides, 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 clearly states the tool searches GleanMark's USPTO trademark database and specifies the return format: citable results with a stable id, human-readable title, and public URL. It is specific about the resource and output, but it does not explicitly differentiate itself from sibling search tools such as search_trademarks or phonetic_search.

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 useful workflow guidance by telling agents to use the fetch tool with a returned id to read the full record, and it notes coverage of 14M+ live and dead USPTO records. However, it does not mention when to prefer this tool over the many search-adjacent siblings, nor does it state exclusions or alternative selection criteria.

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