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

The description conveys the core behavior of center-cropping, but does not disclose whether the crop overwrites the original, creates a new artifact, or requires special permissions. Annotations are all false hints and do not provide this side-effect context, though there is no contradiction with the description.

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 compact, front-loaded, and easy to scan. However, the ratio list repeats the schema enum and the 'Pixels:' phrasing is cryptic, so not every segment adds maximal clarity.

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?

With no output schema and no parameter descriptions, the tool description is thin for reliable invocation. It omits the roles of `creationIdentifier` and `folderReference` as well as any post-crop behavior, so it is stronger for tool selection than for correct parameter construction.

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?

Only `aspectRatio` receives semantic context via 'Center-crop to `aspectRatio`', and the listed ratios merely duplicate the schema enum. The required `creationIdentifier` and optional `folderReference` are completely unexplained, leaving 0% schema description coverage uncompensated.

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 opens with 'Center-crop to `aspectRatio`', a specific verb plus resource and outcome. It also differentiates from sibling tools by explicitly naming `images_resize` and `images_upscale`.

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 'Pixels: `images_resize`. AI upscale: `images_upscale`.' points to alternative tools for non-crop operations, giving useful selection context. It is somewhat telegraphic, but the intended when-to-use distinction is clear enough.

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