add_slice

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

Annotations already establish that this is a mutation (readOnlyHint=false) that is not destructive (destructiveHint=false), which matches an additive 'add' operation. The description adds the duplication path via copyFrom, but says nothing about persistence/save semantics, batch vs live backend implications, or what happens to existing slices - all relevant for an 11-parameter 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?

A single tight sentence with the primary action front-loaded and the alternate mode appended. No filler or restatement of the tool name beyond what is needed.

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?

Adequate but thin for an 11-parameter, nested-object, no-required-parameter mutation tool with no output schema. Important operational context - save/batch behavior and what a call with no arguments does - is left entirely to the schema rather than the description.

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 73%, so the schema already documents most parameters (save, color, pivot, center, sprite, backend, copyFrom). The description only gestures at three of them (center, pivot, copyFrom) without adding format or constraint detail beyond the schema, so it lands at the baseline rather than compensating for the uncovered parameters.

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?

States a specific verb and resource ('Adds a slice') and names the two operating modes: normal add versus duplication via copyFrom. It does not explicitly differentiate itself from the sibling update_slice/delete_slice, though the verb makes the distinction largely inferable.

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 choose this tool over update_slice or delete_slice, and no mention of prerequisites (e.g. that a slice generally needs bounds). The only routing hint is the copyFrom duplication mode, which is described as a capability rather than a when-to-use condition.

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