canvas_export

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

With no annotations, the description carries the full burden; it does disclose the format default and that relative paths resolve against the workspace, which is genuinely useful. It says nothing about overwrite behavior, required permissions, or what is returned on success, which matters for a tool that writes to disk.

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 sentences, front-loaded with the action and with zero filler. The format default and path resolution are packed into the same compact statement.

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 simple two-parameter export tool with no output schema, the description covers the essentials of what and where. It leaves the write-side behaviors (overwrite, result path, failure modes) undeclared, which is a moderate gap given the absence of 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?

Schema coverage is 100%, so both parameters are already documented, and the format enum is fully specified. The description only adds the workspace-relative resolution rule and the default format, which the schema largely covers.

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?

States a specific verb and resource ('Save the board to a file') plus the two supported formats, which is concrete. It does not distinguish itself from the sibling canvas_save, so an agent cannot tell from the description alone which one writes a file versus which one persists state.

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 and no mention of alternatives such as canvas_save or canvas_screenshot, even though the sibling list contains tools that plausibly overlap. Usage is only implied by the word 'Save'.

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