aaddyy_image_compressor

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

No annotations exist, so the description must carry the full behavioral burden. It says the original format is preserved and lists supported formats, but says nothing about whether compression is lossy, whether the source image is mutated or a new artifact is returned, or what the result looks like.

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 short, front-loaded sentences with zero filler; the core action and the preset/format details are stated immediately.

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 two-parameter utility with no output schema and no annotations, the description covers capabilities but leaves the input contract and output behavior unexplained, which is more than a trivial gap even at this low complexity.

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 0%: both 'image' and 'quality' have empty descriptions. The description names the three quality presets but gives no guidance on choosing between them, and gives no hint about what the required 'image' parameter accepts (URL, upload, base64).

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 ('Compress images') plus the quality presets and supported formats, which clearly separates it from siblings like aaddyy_upscale_image and aaddyy_image_to_pdf. It does not name a sibling explicitly, but the operation is unambiguous.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., that an image must be supplied), and no routing against alternatives such as the upscaler or format converters. Only an implicit 'use this to shrink files' is conveyed.

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