Show Image

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds important context about requiring completed images and encoding transforms in the URI query string. It does not contradict the annotations and provides practical guidance on usage constraints beyond the structured data.

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 well-structured and front-loaded with the primary purpose, followed by concise usage instructions and a resource pointer. It avoids unnecessary fluff, though the 'no separate parameters needed' note is slightly redundant given the schema.

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?

Despite lacking an output schema, the description covers when to use the tool, the prerequisite of completed images, the URI format with examples, and how to discover available images. This is sufficient for a one-parameter display tool with supportive annotations.

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 provides 100% coverage of the single 'uri' parameter, and the description adds examples of valid URIs and explains the query-string transform mechanism. While not extensive, the examples and explanation help clarify how to construct the URI, exceeding what the schema alone offers.

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 displays a completed image with optional on-demand transforms, using a specific verb and resource. It distinguishes itself from sibling tools by explicitly limiting use to completed images and referencing check_generation_status for polling.

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 explicitly states when to call the tool ('Only call this for completed images') and how to coordinate with check_generation_status. It also directs users to the image://list resource for browsing IDs, providing clear exclusions and alternatives.

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