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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond that: hard limits (300 topics, 6 levels), validation behaviour ('Refuses mixed indentation and skipped levels with the line number') and the fact that nothing is persisted. It stops short of describing performance or failure modes beyond validation, but the added context is solid.

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 single paragraph is front-loaded with the usage trigger, then inputs, then outputs, then exclusions – a sensible order. It is dense but mostly earns its length; the enumeration of layout names duplicates the schema and could be trimmed.

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 a six-parameter generation tool it covers everything an agent needs: both input forms, size/depth caps, formatting rules, validation failures, output artifacts and explicit non-goals. The return-value sentence is partly redundant given the output schema, but nothing material is missing.

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 each enum already documents its own meaning (layout, theme, page_size), so the schema carries the weight. The description mainly restates the option families ('a layout (balanced, right-tree or org-down), a colour theme and a PDF page size') and repeats the indentation rule (2 spaces or 1 tab) already in outline_text, adding little new semantics.

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 states a specific verb and resource ('mind map ... drawn from an outline or a list of topics and subtopics') and reinforces it with trigger examples like 'turn these notes into a mind map'. The direction of conversion (outline -> map) implicitly separates it from outline_from_mind_map, but that sibling is never named, so an agent must infer the distinction rather than being told it.

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?

It opens with an explicit 'Use this when' trigger covering synonyms (mind map, concept map, brainstorm map, topic tree) plus concrete user phrasings. It also states when NOT to use it: no flowcharts with decisions, timelines, images or cross-branch links, and no saving of maps.

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