Get image

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

Describes that it is a GET request, implying read-only and safe behavior. Lists the specific metadata returned. Could be more explicit about error handling or rate limits, but no annotations exist to contradict.

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?

Concise, front-loaded with purpose, includes examples and cross-reference to another tool and docs. No wasteful sentences.

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?

No output schema, but description explains all relevant return values (metadata, transforms). References alternative tool and documentation for further details. Complete for a simple get-by-id tool.

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 has 100% coverage with parameter description. Description adds value by explaining the return structure and transforms, which relates to the parameter's output.

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?

Explicitly states 'Get metadata (CDN URL, size, MIME type, dimensions) for one PixelVault image by id' with specific verb and resource. Distinct from siblings like list_images, upload_image, delete_image, sign_url, transform_image.

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?

Mentions alternative tool transform_image for building transform URLs, and includes a docs link for further guidance. Does not explicitly list when to use other siblings like list_images, but provides clear context.

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