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

Annotations already cover read-only, idempotent, closed-world and non-destructive semantics, so the description only needs to add context — and it does, with the 300-topic and 6-level limits, the statement that output is re-acceptable by generate_mind_map, and the downloadable outline/OPML artifacts. Return details are partly redundant with the output schema, which keeps it below a 5.

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?

Three sentences, front-loaded with the usage trigger, then inputs/limits, then outputs and exclusions. The middle sentence is somewhat dense with return details that the output schema already covers, but nothing is truly wasteful.

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?

Covers trigger conditions, input shape and limits, output forms, round-trip compatibility with the sibling, and explicit exclusions. For a read-only three-parameter conversion tool with full schema and output schema, nothing an agent needs 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%, giving a baseline of 3, but the description adds a constraint not present in the schema (6-level depth limit) and clarifies the node shape ({text, children}) and that title is the centre topic written as the first outline line. Marginal but genuine value over the schema.

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 inverse operation (mind map → text outline) with concrete output forms (indented/Markdown bullets) and explicitly names its sibling generate_mind_map as the round-trip counterpart. An agent can distinguish it from generate_mind_map from the description alone.

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?

Gives trigger phrases ("give me this mind map as an outline"), an explicit negative boundary ("Does not read images of mind maps or files from other apps"), and names the sibling it complements. When-to-use and when-not are both stated.

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