set_image_size

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only mentions 'updating EMU extent attributes', which is technical but does not explain side effects, permissions, reversibility, or constraints. The output schema exists but is not described. This lacks transparency for a mutation tool.

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 two sentences plus a list, which is concise and easy to parse. The list format for arguments is clear. Minor room for improvement by condensing further, but overall efficient.

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 the basic purpose and arguments, and an output schema exists, so return values are handled. However, it lacks usage context and behavioral details, which are important given the many sibling image tools. It is minimally complete but could be richer.

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 0%, so the description must compensate. It explains rId as 'relationship ID', width_cm and height_cm as 'new width/height in centimetres', adding clarity beyond the schema's simple titles. However, it does not specify constraints (e.g., positive values) or format details.

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 'Resize' and the resource 'embedded image', which is specific. Among sibling tools like get_images, insert_image, set_image_border, this tool is uniquely about resizing images, making its purpose distinct and clear.

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 description gives no guidance on when to use this tool versus alternatives like update_image or set_image_border. It does not mention prerequisites (e.g., needing rId from get_images) or when not to use it. For a tool with many related siblings, this is a significant gap.

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