set_image_size

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

No annotations provided. The description mentions 'EMU extent attributes' but does not disclose side effects, reversibility, permissions required, or constraints on image types. For a mutation tool, more transparency is needed.

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?

Extremely concise: one sentence for the purpose, followed by a structured 'Args' section. No fluff, front-loaded with the key action. Every sentence earns its place.

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?

Given the presence of an output schema (so return values are covered), the description adequately explains the action and parameters. It could mention that the image must already be embedded, but that is implied by the 'rId' parameter. Overall, complete for a simple resize tool.

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 description explains each parameter: rId as 'relationship ID', width_cm and height_cm with units ('centimetres'). With 0% schema description coverage, this adds meaningful semantics beyond the schema's mere property names and types.

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 action ('resize an embedded image') and the mechanism ('updating its EMU extent attributes'). It distinguishes this tool from sibling tools like insert_image, delete_image, set_image_alt_text, etc., which have different purposes.

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?

No explicit guidance on when to use vs. alternatives. However, the purpose is straightforward, and given the sibling list, the context is implicit. Lacks when-not-to-use or prerequisite information.

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