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

Annotations already cover the safe-read profile (readOnlyHint, idempotentHint, openWorldHint), yet the description adds real operational context: private/local addresses are refused, the file is capped at 10 MB, and the viewBox is preserved unless removeViewBox is true. That is meaningful behavior beyond the structured hints, though it doesn't cover failure modes for malformed SVG.

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?

Five short sentences packed with constraints, front-loaded with the core action and input methods. The closing sentence about return values is largely redundant given a declared output schema, but no sentence is filler.

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 nested-object tool with an output schema present, the description covers input forms, security limits, and the viewBox default, so an agent can invoke it confidently. The remaining gap is the unmentioned precision and removeDimensions parameters, which the schema also leaves undocumented.

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 only 40%, so the description must carry more weight. It does explain svg vs. file, URL/base64 input, the 10 MB cap, and the removeViewBox flag, but it says nothing about precision or removeDimensions, leaving two of five parameters semantically undefined in both the schema and the description.

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 and resource ('Minify an SVG with SVGO') and extends it with the accepted input forms, so the agent knows exactly what operation is performed. It does not explicitly distinguish itself from the sibling minify_code, but the SVG-specific scope makes the boundary reasonably clear.

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?

The description tells the agent how to supply input (markup, base64 data, or a public URL), which implies when the tool applies. However, it never states when to use this over minify_code or compress_image, nor any exclusion conditions beyond the private-address refusal, so usage is only implied.

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