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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety burden is partly covered. The description adds that print-area context is preserved, but it does not explain the extent of mutation, reversibility, or that supplied design patches can overwrite session content.

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 front-loaded sentence with no filler. The core action appears immediately, and the print-area constraint is included without unnecessary exposition.

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?

The description is adequate given the rich schema and destructive annotations, but it is thin for a complex nested-options mutation tool. It does not clarify what 'existing crop options' means or how the crop interacts with session content, leaving the schema and annotations to carry significant context.

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?

Schema description coverage is 100%, so the baseline is 3. The description references 'existing crop options' and 'print-area context,' which loosely maps to the options object, but it adds no concrete detail about crop fractions, placement, or required session identifiers beyond what the schema already provides.

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 states a specific verb and resource: 'Crop the selected image.' It also scopes the operation by mentioning existing crop options and print-area context, so an agent can distinguish it from siblings like flip_image or resize_element. It stops short of explicitly naming those alternatives.

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 implied by 'Crop the selected image,' but the description does not explicitly say when to choose this over flip_image, rotate_element, or resize_element, nor does it state when not to use it. The print-area constraint provides some context but not routing guidance.

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