gdx-image-webify

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

No annotations are provided, so the description must disclose behavioral traits. It merely states conversion capabilities and does not mention overwrite behavior, quality handling, error conditions, or whether original files are preserved. The safety-related forceOverwrite parameter is not referenced, leaving significant gaps for a tool that writes files.

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?

Two sentences, front-loaded with the core action. It is efficient, readable, and uses no wasted words.

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 conversion tool with 5 parameters including the safety-critical forceOverwrite, the description is minimal. It lacks information about behavior, limitations, return values, and usage context, making it incomplete for an agent to safely operate the tool.

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%, so the baseline is 3. The description reiterates formats that are already documented in the schema but does not add any parameter-specific semantics beyond what the schema already covers.

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 clearly states the tool converts images to different formats using sharp, specifying supported input formats (.jpg, .jpeg, .png, .webp, .tiff, .avif, .gif, .svg) and output formats (webp, avif). It is specific and action-oriented, leaving no doubt about the tool's function.

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 when image format conversion to webp/avif is needed, but it provides no explicit guidance on when to use this tool versus alternatives, prerequisites, or edge cases. With no siblings listed, a clear use-case statement is missing, though the conversion purpose is evident.

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