pdc_convert

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

With no annotations, the description fully discloses behavior: it validates known constraints before conversion, returns structured violations instead of a broken file, reports non-fatal warnings (odd coordinates), and on failure lists exactly what to fix. It also states the tool 'never guesses at a lossy conversion,' setting explicit expectations about failure handling.

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 dense but well-organized, with clear sections: purpose, validation behavior, supported/unsupported features, success/failure output, and next-step advice. Every sentence adds value, and the structure allows an agent to quickly extract the important constraints and response contract.

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?

Given the tool's complexity (format conversion with many constraints), the lack of an output schema, and zero annotations, the description is remarkably complete. It covers input requirements, failure modes, success output fields, warnings, and remediation steps. An agent has enough context to decide when to invoke this tool and what to do with the result.

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?

The schema has only one parameter, svg_text, with no description (0% coverage). The description compensates by explaining what the SVG input should contain—supported element types, unsupported transforms, and required pre-processing (flatten curves). It implicitly defines svg_text as the SVG XML string and provides concrete guidance on its valid content, though it does not explicitly say 'svg_text is the SVG source code.'

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 a specific verb+resource: 'Convert an SVG icon/vector to a Pebble Draw Command (.pdc) file.' This clearly distinguishes the tool from siblings like image_quantize or font_plan, which address different steps in the Pebble design pipeline.

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 gives abundant context on appropriate use: it enumerates supported SVG elements, lists unsupported features (gradients, masks, clip paths, etc.), and instructs the user to 'flatten curves first' and remove unsupported elements before retrying. It stops short of explicitly naming alternative tools or saying 'use this tool instead of X', but the constraints provide clear when-to-use guidance.

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