svg_validate

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does disclose a valuable non-obvious behavior: paint detection reads style= attributes, presentation attributes, and inherited paint, preventing false empty reports for Inkscape-authored files. However, it does not mention return format, side effects, permissions, or what happens on validation failure.

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?

The description is two sentences with no filler: the core purpose and operation list are front-loaded, followed by a single high-value behavioral note about paint detection. Every clause earns its place, and the structure makes the operation vocabulary immediately visible.

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?

Although the operation list is useful, the agent cannot determine which parameters are required for each operation—for example, whether validate needs input_path, whether size_limits needs max_dimension/max_file_size_mb, or whether audit_web needs a pattern. With no annotations and no output schema, the missing operation-to-parameter mapping and undefined return behavior are significant gaps for correct invocation.

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%, and the description adds the allowed operation values that the schema defers to ('See the tool summary for valid values'). It also clarifies that audit_pack operates on a whole directory. The remaining parameters are already described well in the schema, so the description appropriately supplements without redundancy.

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 description opens with 'SVG quality assurance' and then lists six concrete operations (validate, viewbox, stroke_fill, size_limits, audit_web, audit_pack), making it clear this is a multi-mode validation/audit tool. It does not explicitly contrast with svg_analyze, but the QA framing and operation names distinguish it from editing, animation, and export 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?

The description implies usage through terms like 'quality assurance', 'audit_web', and 'audit_pack (a whole directory)', so an agent can infer this is for validating or auditing SVG files. However, it never states when to prefer this tool over svg_analyze or svg_optimize, nor does it list exclusions or alternative conditions.

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