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

Goes well beyond the annotations by disclosing export semantics: only the overlay flag reaches the WordPress export, ratio/position are canvas-only, and alt text propagates to WordPress and Astro exports. However, despite destructiveHint=true it never states what a call destroys or whether omitted fields are reset, leaving the destructive trait itself unexplained.

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?

Front-loads the core purpose before the export caveats, and each sentence carries non-redundant information about export behavior. It is dense and slightly long, with capitalized emphasis, but nothing is padding.

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?

No output schema, and the description covers the non-obvious export behavior and alt-text propagation thoroughly. The remaining gap is the destructive/overwrite behavior implied by annotations but never spelled out, which an agent mutating existing settings would want to know.

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?

With 67% schema coverage, the description usefully explains the two undocumented params (ratio as aspect ratio, position as the focal point kept when the slot crops) and adds export meaning to overlay and alt beyond the schema's field-level text. It adds genuine semantic value rather than restating the schema.

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?

Names a specific verb+resource (set how a picture sits in its slot) and enumerates exactly which display aspects it controls: aspect ratio, focal point/crop position, overlay darkening, and alt text. It also distinguishes itself from uichemy_crop_image by naming that sibling, so an agent can route correctly without opening a schema.

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?

Explicitly states when this tool is the right one versus the alternative: use uichemy_crop_image to change the picture itself, and use uichemy_validate to find pictures missing alt text. It also scopes usage by export target (canvas-only settings vs the overlay flag the WordPress export reads), which is exactly the routing guidance an agent needs.

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