tsdr_get_trademark_image

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

No annotations are provided, so the description carries the full burden. It discloses the return format (dictionary with base64-encoded image data) and the input requirement, but does not mention error behavior, authentication, rate limits, or what happens if no image exists. This is adequate but not rich.

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 compact and well-structured with clear sections for purpose, usage trigger, arguments, and returns. Every sentence adds value, and there is no redundant or vague filler.

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 one-parameter retrieval tool, the description covers purpose, when to use, argument format, and return type. It does not mention edge cases like missing images or alternative tools, but the overall context is sufficient for basic invocation.

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 schema only defines serial_number as a string with no description. The tool description adds meaningful semantics by specifying '8-digit application serial number' and providing an example ('78787878'), which goes beyond the schema and helps the agent format the parameter correctly.

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 retrieves the mark image (drawing) for a trademark as base64, using a specific verb and resource. It distinguishes itself from sibling tools like tsdr_get_trademark_status and tsdr_list_trademark_documents by focusing on image retrieval.

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 includes an explicit 'USE THIS TOOL WHEN' section: 'You need the visual representation of a design mark or stylized word mark.' This provides clear context for when to use it, though it does not mention when not to use it or name alternative tools.

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