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

The description adds behavior beyond annotations by explaining the default return mode (inline Markdown) and the binary artifact behavior (base64 plus workspace link). Since annotations already indicate idempotence and non-destructiveness, this focused extra context is valuable.

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 sentences, tightly written, front-loading the core action and then adding the return format distinction. No filler or redundant repetition of the title.

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 no output schema, the description still provides enough: what is generated, how to identify the target, supported formats, and the return mode for each format. A complete call is derivable without additional assumptions.

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?

The schema covers all 4 parameters with descriptions, so the baseline is solid. The description adds useful context on how formats behave and clarifies that both exact ID and fuzzy name are valid identifiers, which helps an agent select the right operationally.

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 uses a specific verb and resource: 'Generates a branded profile for one existing Mind.' It clearly distinguishes itself from sibling export tools (export_group, export_panel, export_heatmap) by naming the target resource and the identifier mechanism.

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?

The description gives clear context: use this when exporting a profile for an existing Mind, identified by exact ID or fuzzy name. It does not explicitly name sibling export tools as alternatives, but the intended scope is unmistakable.

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