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

No annotations are provided, so the description carries the full burden. It states the transformation (messy problem -> clean issue tree) but discloses nothing about structure, depth, mutability, or what the response looks like for a tool with no output schema.

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?

One tight sentence with the outcome front-loaded and zero filler. It is well-sized for the tool's simplicity, though there is little structure to speak of.

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 simple one-input tool the bar is low, but with no output schema the agent gets no sense of the return structure, and no comparative context against 18 sibling frameworks. The description leaves the agent under-equipped to choose and predict.

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?

Single parameter with 100% schema coverage; the schema already documents 'Your problem, decision, project, or question.' The description adds no syntax, format, or length guidance beyond the schema, so baseline 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?

Specific verb ('Break down') + resource ('MECE issue tree') + input scope ('messy business problem'). It distinguishes itself from the many sibling framework tools by naming the exact framework (MECE issue tree vs. SWOT, Five Whys, etc.), though it never states why an agent should pick it over those 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?

No when-to-use, when-not, or alternative guidance. 'Messy business problem' implies a decomposition task, but with 18 sibling framework tools the description gives the agent nothing to route on beyond the framework name itself.

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