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

No annotations are supplied, so the description carries the full disclosure burden. It usefully names the four output representations, which is the main behavioral trait, but it never states that export is a non-mutating read operation, nor whether the result is returned inline, as a file handle, or as a downloadable URL.

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?

A single front-loaded sentence with zero filler. The verb and resource come first, followed immediately by the format list, so an agent gets the essential information in one read.

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?

The tool is simple (2 required params, no nesting, no output schema), and the description covers the format dimension. However, with no output schema, it should clarify what exporting actually yields — a string, a file path, or a rendered artifact — which is the key unknown for a caller.

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 50%: projectId is documented in-schema (including the Canvas URL trick), while format is a bare enum. The description echoes the four enum values as output types, adding mild clarity but no new semantics beyond the names themselves.

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?

Uses a specific verb ('Export') on a specific resource (the mind map) and enumerates the four concrete output formats. An agent can distinguish it from read-oriented siblings like get_mindmap or mutation tools, though it never names a sibling explicitly.

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?

States what it does but not when to choose it over get_mindmap, nor how to pick among the four formats. There are no prerequisites, no exclusions, and no context about when exporting is the right call versus reading the map in place.

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