mermaid_to_excalidraw

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

No annotations are present, so the description bears full responsibility. It discloses the stub behavior and exactly what return format to expect (success: False, error_type: 'not_implemented', suggestions), plus explains the planned implementation. No contradictions.

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?

The description is front-loaded with the purpose and the critical 'NOT IMPLEMENTED' notice. The implementation-plan paragraph adds context but is arguably unnecessary; still, the overall structure is organized and not overly verbose.

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 an unimplemented tool, the description fully covers what an agent needs to know: the tool will fail gracefully with a specific error format. The optional rendering mention is vague since there is no render parameter, but that is minor given the not-implemented status.

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 input schema already provides clear descriptions for both parameters (output_path and mermaid_source) with 100% coverage. The description does not add additional parameter-level meaning, so the baseline of 3 applies.

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 clearly states the intended function: converting Mermaid diagrams to Excalidraw elements and optionally rendering. It is specific and distinguishes from sibling tools (status, render_svg, batch_render).

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?

Explicitly states 'NOT IMPLEMENTED YET', which is a clear instruction that the tool should not be used for actual conversions. While it doesn't name alternatives, it provides strong contextual guidance on when to avoid the tool.

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