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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it states the core operations, it omits any information about limits, file handling, output format, or side effects (e.g., whether it overwrites images or processes in-browser only). This is a significant gap for a tool that manipulates user 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 a single, efficient sentence that front-loads the key features (white background, shadow, square crop) and includes a parenthetical noting it's browser-based. Every element adds value.

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 simple zero-parameter nature, the description gives a reasonable overview. However, it lacks differentiation from similar sibling tools like bg-remover-pro or smart-resize, and does not explain return values or any processing constraints. For a complete picture, more details on input/output would be helpful.

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 tool has zero parameters, and the schema is empty, so there is nothing for the description to clarify. The baseline of 4 is appropriate since no parameter information is needed.

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 states the tool's function: batch processing product images with white background, shadow, and square cropping. This is a specific verb+resource combination ('一括加工' = batch process) and distinguishes it from siblings like bg-remover or image-crop.

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 phrase '出品画像を一瞬で整える' (instantly tidy up product images) implies a clear use case for e-commerce listings. However, it does not explicitly mention when not to use it or suggest alternatives, such as using bg-remover separately or image-crop for non-square crops.

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