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

The description adds genuinely useful context beyond annotations: a fixed 5-stage progressive output with an animated reveal, and a 15-coin cost. Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so this is solid but not exceptional; it does not say whether the diagram is persisted, returned as images, or editable afterward.

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?

Four short sentences, front-loaded with the core action, then output shape, then cost. Each sentence carries information; only the 'and more' trailing clause is filler.

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 only two parameters and annotations present, most of the burden is light, but there is no output schema and the description never says what the caller receives (image URLs, a diagram ID for edit_excalidraw, a session link). That missing hand-off detail is the one real gap for an agent that may need to edit afterward.

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 description coverage is 100%, with both prompt and ai_chat_context documented in-schema, so the baseline is 3. The description mentions 'any concept' and diagram categories but adds nothing about how to shape the prompt or when ai_chat_context matters.

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 and resource ('Create a hand-drawn style diagram using Excalidraw') and enumerates concrete artifact types (flowcharts, mind maps, math visualizations, system architectures). The 'hand-drawn style' qualifier and the Excalidraw name separate it cleanly from create_infographic and the other create_* siblings.

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?

There is no guidance on when to pick this over create_infographic, study_concept, or edit_excalidraw. 'For any concept' is the opposite of a selection criterion, and no prerequisites or exclusions are given.

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