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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing behavioral. It doesn't say whether the export is a pure read, whether output is returned inline or written to disk, whether large maps are truncated, or what the caller receives for each format.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Nothing in it is redundant or padded.

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 (two required parameters, one enum, no output schema), so a short description is defensible. Still missing is any statement of what an export call actually returns or produces, which matters most for a tool whose entire purpose is producing output.

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 the schema, while the description's enumeration of JSON/Markdown/SVG/Mermaid effectively explains the format enum's meaning. Beyond naming the four targets, it adds no detail on fidelity, size limits, or format-specific caveats.

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 (Export) and resource (the mind map) plus the four target representations, which is enough for an agent to distinguish it from get_mindmap or create_mindmap. It doesn't explicitly name a sibling or scoping rule, so it falls just short of a 5.

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?

Usage is only implied: the agent infers 'use this when you need serialized output in a specific format.' There is no statement of when to prefer this over get_mindmap, nor any prerequisite or exclusion.

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