set_image_sizing

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

Given no annotations, the description carries full burden. It discloses idempotency and return value for same input, but fails to mention that this tool likely requires an active editing transaction (as many sibling set_* tools do). No side effects or permissions are mentioned.

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?

Three sentences, front-loaded with purpose, then enum details, then idempotency. No filler. Each sentence adds distinct 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?

The description covers purpose, enum semantics, idempotency, and minimal return info. However, it omits the editing transaction context (likely needed) and doesn't explain the path parameter or any prerequisites. Given no output schema and 3 params at 0% coverage, it is somewhat incomplete.

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 coverage is 0% so description must compensate. The enum values are well-explained, but path and image_name parameters are not described at all (path is ambiguous). The description adds some value for sizing but not for the other required parameters.

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 verb 'Set' on resource 'Image Sizing', enumerates all four sizing options with brief definitions, and distinguishes itself from sibling tools like set_image_action and set_image_source by focusing solely on sizing.

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 the tool name and description, but no explicit guidance is given on when to use this versus alternatives (e.g., set_image_source). The idempotency note adds value but does not help in choosing between tools.

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