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

Annotations already declare readOnlyHint and idempotentHint, and the description adds real behavioral context beyond them: inference is expected rather than clarification questions, empty `strengths` is legal, and the user can adjust afterward via the builder Edit link. The operational rule about always surfacing the image link — because inline chat images cannot be saved — is a genuinely non-obvious behavioral detail. It stops short of stating what the tool returns (inline render vs. URL vs. both) which is the one loose end.

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?

Purpose and alternative routing are correctly front-loaded, but the body is a single dense paragraph with decorative wording ("softly tinted panel with its big coloured letter", "slide-deck-quality") that costs tokens without helping invocation. The high-value operational rules — inference over questions, the mandatory image link — are buried mid-paragraph and at the very end rather than surfaced structurally.

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 12-parameter tool with a nested colors object, no output schema and no enums, the description covers what matters: required vs. optional quadrants, content length limits, inference policy, and post-generation handoff. The one gap is that with no output schema, the description never states the shape of the response it insists the agent share, so the agent must infer what the "image link" is a field of.

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%, so the baseline is 3 and the bar for credit is higher. The description does add content guidance the schema lacks — infer 3–5 bullets per quadrant, keep them roughly 3–8 words, one-sentence conclusion, fill all four quadrants — which is useful. But it never touches the layout parameters (width, colors, palette, labels, credit, title, subject) that make up most of the 12-parameter surface.

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 opening sentence gives a specific verb and deliverable ("Generate a slide-deck-quality SWOT analysis") and then defines the exact output artifact — a 2×2 grid with named quadrants and their positions. It explicitly names the sibling tools it is not (create_five_forces, the Harvey ball matrix, an issue tree), so an agent can route on name 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?

It enumerates the subjects it fits (company, product, team, project, person) and the use cases (strategy, business-plan, marketing, coursework), then names three alternatives with the condition that selects each: five forces for industry-level pressure, Harvey matrix for scoring options against criteria, issue tree for decomposing one problem. This is the explicit when/when-not/alternative pattern.

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