tool_image_compress

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only lists inputs and outputs, without any information about side effects, lossy/lossless nature, quality ranges, format constraints, or what the 'info' output contains. This is insufficient for a tool that manipulates images.

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 very short, but its brevity reflects under-specification rather than conciseness. The bullet list merely echoes the schema and does not provide explanatory sentences that earn their place. It lacks a clear narrative of the tool's purpose and behavior.

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 has 4 parameters, a nested file object, no output schema, and no annotations, the description is severely incomplete. It does not explain the return value 'info', the valid output formats, quality semantics, or any edge cases. The tool's behavior is only vaguely implied by its name, leaving significant information gaps.

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?

While the schema descriptions cover 100% of parameters, the description fails to add meaning beyond them. It repeats the same minimal labels ('Quality', 'Format') and omits the 'info' parameter that appears in the schema, potentially confusing users. No details on quality values, format options, or file structure are provided.

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 consists mainly of the heading 'Image Compress' followed by parameter/output lists, which essentially restates the tool name without adding specific functionality details. It does not clearly explain what compression entails or how it differs from sibling image tools like tool_image_editor.

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 guidance on when to use this tool versus alternatives. No mention of use cases, limitations, or instructions for choosing compression parameters. The description provides no context for when to prefer this over other image-related tools.

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