export_texture

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It states that the tool exports but does not mention side effects such as writing a file (for png_file), encoding specifics for data URIs, or whether the operation is safe/reversible. The required file_path for png_file is only in the schema, not the description. This is a significant gap for a tool that creates artifacts.

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 a single sentence that front-loads the primary action and lists all possible formats. Every word is informative; there is no filler or redundancy. It is appropriately compact for a tool whose schema covers the details.

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 moderate complexity (4 parameters, no annotations, no output schema), the description is minimally sufficient to understand the core capability, but it omits important contextual details such as what the tool returns (if anything), how file writing behaves, and any constraints beyond the schema. For an export tool, an agent might need to know whether it returns the data or just confirms success.

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 description coverage is 100%, so the schema already documents all parameters. The description merely repeats the format enum in prose and does not add meaning about scale or file_path beyond what the schema provides. It meets the baseline for full coverage but adds little value.

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 a clear action ('Exports the pixel canvas') and enumerates the four output formats (PNG file, Base64 Data URI, ASCII preview grid, JSON grid). This distinguishes it from sibling tools, none of which focus on canvas export. However, it refers to 'the pixel canvas' without explicitly mentioning that the target is identified by canvas_id, which is slightly ambiguous.

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 guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. For instance, it doesn't mention that export is the intended way to retrieve canvas content for external use, nor does it contrast with get_canvas_info. The agent is left to infer usage from the name and schema.

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