resize_canvas

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

No annotations provided, and description fails to disclose side effects (e.g., modifies file in-place), behavioral details (e.g., interpolation method), or requirements (e.g., file must be open). 'Scale' is vague regarding how content beyond new dimensions is handled.

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?

Two sentences plus structured argument list. No redundant information, but could be more efficient by integrating param descriptions into the main sentence.

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, yet description does not mention return values or success/failure indicators. Lacks info on prerequisites (e.g., file open state) and relationship to sibling tools. Incomplete for a mutation 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?

Schema has 0% description coverage; description adds brief but clear meaning for each parameter (filename as Aseprite file, width/height in pixels). However, lacks constraints (e.g., positive integers) and filename 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?

Description uses specific verb 'scale' and resource 'canvas and all its content', clearly distinguishing it from sibling tools like crop_canvas (which removes content) and create_canvas (which creates a new canvas).

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 guidance on when to use this tool versus alternatives (e.g., crop_canvas), no prerequisites mentioned, and no scenarios where this tool is inappropriate.

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