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

No annotations are provided, so the description carries the full burden. It discloses that processing happens in the browser (implying local/no-upload) and mentions the target-size feature. However, it does not describe output format, quality preservation, or file-handling behavior, leaving some behavioral aspects unspecified.

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 a single, compact sentence that conveys purpose, supported formats, context, and a key capability. It contains no unnecessary words, and the bilingual structure is efficient.

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?

As a zero-parameter, browser-based utility with no output schema, the description covers the core behavior and a notable feature. It omits details like how results are delivered, but given the tool's simplicity, the description is adequately complete.

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?

The input schema has zero parameters, and the description adds no parameter-level details. Per the baseline for 0-param tools, this is acceptable; the mention of '目標サイズ指定' (target size specification) is a tool feature rather than an input parameter.

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 specifies the action (軽量化 = compress/reduce size) applied to specific image formats (JPG/PNG/WebP), and adds the context of browser-based processing. This distinguishes it from sibling tools like image-resizer or image-crop, making the purpose 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?

The description establishes when to use the tool: for compressing JPG/PNG/WebP images in the browser, with optional target-size control. It does not explicitly name alternatives or exclusions, but the given context is clear enough for selection among many image-related tools.

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