delete_slice

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that — it says nothing about whether deletes are undoable, that the operation mutates a sprite file, or how batch/live mode affects persistence. No contradiction with annotations, but no value added either.

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?

A single three-word sentence is not conciseness — it is under-specification. There is nothing front-loaded or structured, just a name restatement.

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 destructive mutation tool with four parameters, live/batch execution modes, and a save-to-file side effect, this description is far too thin. The absence of an output schema is fine, but the critical batch persistence behavior and slice-identifier semantics are left entirely unexplained.

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 75%, but the one required parameter (slice) has no description in either the schema or the description, so the agent cannot tell whether it takes a name or an index. The description contributes zero parameter meaning and does not compensate for the gap.

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?

"Deletes a slice." restates the tool name delete_slice with no additional specificity — it is essentially a tautology. It gives no hint of scope (which slice, how identified) or how it differs from sibling slice tools such as add_slice, update_slice, or delete_frames.

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?

There is no guidance on when to use this tool versus alternatives like update_slice or delete_frames, no prerequisites, and no mention of the live-vs-batch distinction. An agent must infer everything from the schema.

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