export_blueprint_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 explains the parameters and return value well, but does not disclose side effects (e.g., file creation on disk, permission requirements, or any destructive behavior). The description is accurate and non-contradictory.

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 with bullet-like Args and Returns sections, front-loading the core action. Every sentence provides essential information; no fluff. It's concise yet comprehensive.

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?

Given the tool's complexity (5 params, 1 required, no enums, has output schema), the description covers the action, parameters, and return format adequately. It doesn't explain file overwrite behavior or disk space implications, but these are minor. The output schema exists but the description still explains return values, which is helpful.

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 description adds significant meaning beyond the input schema, which has 0% schema description coverage. It explains each parameter's purpose, allowed values (format options), and constraints (scale/transparent for PNG only). The output_path default is specified. This compensates for the lack of schema descriptions.

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 renders a Cloudcraft blueprint to an image file on disk, specifying the verb 'render' and the resource 'blueprint image'. It distinguishes itself from siblings like get_blueprint (which likely returns JSON) and snapshot_aws (AWS snapshot).

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 provides default values and allowed formats but does not explicitly state when to use this tool versus alternatives like get_blueprint or list_blueprints. The return format is described, but no guidance on prerequisites or when not to use is given.

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