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

Annotations already cover readOnlyHint, idempotentHint and destructiveHint, so the safety profile is handled. The description adds useful parity context ('as the Export menu does'), implying the output matches the UI's export, but says nothing about what is actually returned (file bytes, URL, base64) or size/time limits for large boards.

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 front-loaded sentence with the action, resource, and format set; nothing 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?

With no output schema, the description carries the burden of explaining the return value, and it does not — the agent cannot tell whether it receives a document string, a file reference, or a download link. Everything about the inputs is complete, but the output side is a notable gap for an export tool.

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% and both parameters are described there, so the description's format list merely restates the enum. It adds no syntax or behavioral hint beyond the schema (e.g. whether png truncates content).

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?

Specific verb (Export) + resource (a board) plus the exact output formats and a familiar frame of reference ('as the Export menu does'). No sibling tool performs exporting, so an agent can immediately place it in the toolset.

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 by the name and the 'Export menu' parallel; there is no explicit statement of when to prefer this over, say, get_board for reading content, nor any prerequisites (permissions, board state). Since no true alternative exists for producing a file, the omission is forgivable but real.

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