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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the source (USPTO ID Manual), the surcharge-free aspect, and that curly-brace entries are fill-in templates. This goes beyond the annotations and helps the agent anticipate the output format and placeholder behavior.

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 three sentences and every sentence earns its place: the first states the core function, the second provides a critical usage rule, and the third explains the output format and placeholder convention. It is front-loaded with the main verb and resource, with no fluff or repetition of schema fields.

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 that an output schema exists and annotations cover safety, the description is largely complete. It covers the source, the usage rule about distinct product lines, and the placeholder behavior. It doesn't explain the returned Term IDs' structure, but the output schema presumably covers that. The only minor gap is not distinguishing when to use this tool versus validate_gs_description, but that's a usage-guidelines nuance rather than a completeness failure.

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%, so the schema already documents all four parameters with descriptions. The tool description reinforces the query semantics by specifying 'plain words' and 'call once per distinct product/service line,' but this aligns with the schema's own description of the query parameter. No additional parameter-level detail is provided beyond what the schema contains, so a 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 begins with a specific verb and resource: 'Search the USPTO Trademark ID Manual' by plain words, clearly distinguishing it from other tools. The scope of returning selectable Term IDs and the mention of pre-approved, surcharge-free identifications further clarifies the tool's unique purpose.

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?

It provides explicit usage guidance with 'Call once per distinct product/service line' and gives a concrete example. While it doesn't explicitly name alternatives like validate_gs_description, the instruction to call once per line is a clear 'when to use' directive. It lacks an explicit when-not statement, but the context is strong enough for most use cases.

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