delete_image

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

With no annotations, the description carries burden. It discloses that the drawing and relationship entry are removed, which is helpful, but does not mention side effects, undoability, or required document state. Adequate but not thorough.

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 parameter description. No filler words. Front-loaded with the action. Highly 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?

For a simple one-parameter tool, the description is fairly complete: it explains the operation and the parameter. Output schema exists but not needed. Could mention where to obtain rId, but overall adequate.

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% coverage, but description adds meaning: 'relationship ID of the image to delete (e.g. 'rId5')'. Provides concrete example and clarifies the parameter's role, compensating for missing schema descriptions.

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?

Clearly specifies 'Remove the drawing containing the image' and 'removes the relationship entry', distinguishing it from siblings like remove_hyperlink or insert_image. The action and target are unambiguous.

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 this tool versus alternatives (e.g., remove_hyperlink, update_image). No mention of prerequisites or context like needing the rId from get_images.

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