tm_get_trademark

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

No annotations are provided, so description carries the burden. It indicates the response is normalized and that it is not the authoritative live status, giving useful behavioral hints, though it does not explicitly note read-only nature or potential side effects.

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 concise and well-structured with sections for usage, arguments, and returns, making it easy to parse and apply.

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?

Return value is described as 'Normalized response with the trademark record,' which is sufficient for a basic understanding, though more detail could be beneficial if the output schema is complex.

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?

The parameter serial_number is fully explained as an 8-digit application serial number with an example, making its meaning and format unambiguous despite the schema lacking a description.

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?

Clearly states the function: retrieving a trademark's search-index record by serial number, and distinguishes it from other tools like tm_search_trademarks and tsdr_get_trademark_status.

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 provides when to use this tool (having a serial number from tm_search_trademarks and wanting the full indexed record) and when to prefer an alternative (tsdr_get_trademark_status for authoritative live status).

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