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

With no annotations, the description carries the transparency burden. It discloses that the tool is browser-based and uses AI for subject detection and smart crop, which gives some insight into behavior. However, it does not clarify whether images are processed locally or uploaded, nor does it mention output format or limitations.

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 sentence plus a parenthetical, front-loaded with the core function and followed by the browser-based context. Every word earns its place with no fluff or repetition.

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?

For a tool with no schema parameters and no output schema, the description is the sole source of functional context. It covers the main capability but omits practical details such as input methods, output format, batch size limits, or whether there is an upload/save step. It is minimally adequate but leaves 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?

The input schema is empty, so there are no parameters to describe. The baseline for zero parameters is 4, and the description correctly omits parameter details that do not exist. No additional semantics 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 image resizing with AI subject detection and smart crop. It uses a specific verb (resize) and resource (images), and distinguishes itself from siblings like image-resizer and image-crop by highlighting the AI and batch capabilities.

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 implies use cases (batch processing with subject-aware cropping) but does not explicitly state when to use this tool over alternatives like simple image-resizer or image-crop. The browser-based note hints at a client-side tool, but no direct guidance on when or when not to use is provided.

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