Get image

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds context not in the annotations - provider scopes, locks and credits apply - which flags auth and cost implications, but it stays generic (no specific scope name or credit count) and says nothing about return shape or error 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?

Two short clauses, endpoint front-loaded, no filler. Efficient, though the brevity contributes to the gaps rather than being purely a virtue.

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 read-by-identifier tool with no output schema and no annotations describing the payload, the description should indicate what an image record contains or how it relates to get_image_template / list_images. It omits all of that, leaving the agent to infer the response entirely.

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 only 50%: the 'account' parameter is documented in the schema, but 'uid' has no description there, only a pattern and length bounds. The description merely echoes '{uid}' as a path segment and adds no meaning about what the identifier is (image uid vs. template uid) or what 'account' scoping does.

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 states the exact endpoint 'GET /v5/images/{uid}', which is a specific verb+resource and clearly identifies a single-image fetch. It does not differentiate itself from siblings such as list_images or get_image_template, but the endpoint path makes the target resource unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives like list_images for enumerating images. The only usage signal is the trailing 'Read operation', which is implied by the annotations rather than the text.

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