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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds one piece of context beyond the structured fields: the call yields a persistent artifact plus an edit link in Xenition. It does not explain that a new artifact is produced per call despite idempotentHint=false, which would have earned a higher score.

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, no filler, and the trigger condition is front-loaded ahead of the output note. Every clause carries information an agent can act on.

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 at full schema coverage, an output schema present, and clear annotations, the description is sufficient to invoke the tool correctly. The remaining gap is minor: no guidance on how rich the brief should be or what happens to previously created diagrams.

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% for both parameters, so 'brief' and 'title' are already fully documented in the schema. The description's phrase 'created from a description' only loosely gestures at the brief parameter and adds no format, length, or content guidance.

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 ('diagram ... created from a description') and enumerates the sub-types it covers (flowchart, sequence, architecture, ER, mind map), which separates it from generic artifact creators like create_document or create_image. It stops short of explicitly naming a sibling it replaces, so it lands just below the top mark.

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 opening clause 'Use this when the user wants a diagram ... created from a description' is an explicit usage trigger, and the enumeration of diagram kinds further narrows the case. There is no when-not guidance or named alternative (e.g., whether to prefer create_document for prose or create_slides for decks).

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