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

With no annotations, the description carries the full burden, and it discloses that this is a static read (no parameters, fixed three presets) whose values are kept in parity with the Compresseur Local web app, implying authoritative, stable results. It stops short of explicitly stating read-only/side-effect-free behavior, but the 'List' framing plus fixed content makes the safety profile clear.

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 returned content and the preset names, with no filler. The trailing 'Takes no parameters' slightly duplicates the empty schema but is a cheap disambiguation.

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?

No output schema exists, so the description must convey the return shape, and it does: three named presets, per-preset quality and dimension caps, notes, and max input size. That is everything an agent needs to decide whether to call it and how to use 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?

Zero parameters, so baseline is 4; the description confirms 'Takes no parameters,' removing any ambiguity about whether filtering or preset selection is possible at call time.

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 (List) and resource (compression presets) and enumerates the three preset names, so an agent knows exactly what it gets. It does not explicitly contrast itself with compress_file or estimate_compression, but the reference-data framing is unmistakably distinct from those action tools.

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?

Usage is only implied: an agent can infer this is a lookup to call before compress_file to learn preset values, but the description never says when to use it or when to prefer estimate_compression. No exclusions or prerequisites are stated.

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