image.compress

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

No annotations present. Description only mentions input methods and output encoding, but fails to disclose compression algorithm, lossy/lossless behavior, metadata handling, size limits, or typical compression ratio.

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 concise sentences, no redundancy, immediately states purpose and key usage rule.

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 no annotations and no output schema, description is insufficient for a 6-parameter tool. Missing parameter semantics, behavioral details, and response structure.

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?

Description adds meaning by specifying exclusivity constraint for url and imageBase64, but does not explain other parameters (lossy, effort, format, quality) beyond schema. Schema coverage is 17%, leaving most parameters undocumented.

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?

Description clearly states verb 'compress' and resource 'image', specifies two input methods (URL or base64) and output format (compressed bytes). No sibling with similar 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?

Description explicitly guides that exactly one of url or imageBase64 must be provided. However, lacks guidance on when to use compression vs alternatives or when not to use.

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