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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lowered. The description still adds genuine behavior beyond that: unavailable variants throw an error that enumerates the available ones, and the output is described as paste-ready optimized markup. No rate limits or size caveats, but strong for this tool type.

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 tight sentences, all front-loaded: purpose, stack routing, prerequisite. Zero filler and no repetition of schema content.

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?

Though there is no output schema, the description explicitly characterizes the return value (raw optimized SVG markup) and specifies failure behavior and a prerequisite. Nothing an agent needs to invoke this correctly 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 the variant enum is fully documented in the schema, so the schema carries the parameter burden. The description implies the variant concept and points to get_logo for discovery, but adds no syntax or default meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 (get) and resource (raw, optimized SVG markup of one logo variant), plus the intended consumption targets (inline HTML/JSX/Vue/Svelte or .svg file). It explicitly distinguishes itself from the sibling get_logo_component, so an agent can route correctly without opening both schemas.

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?

Names the condition for use (non-React stacks or a single file), names the alternative (get_logo_component for React), and gives a prerequisite (call get_logo first to see available variants). When/when-not/alternative are all present.

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