Apply an edit to an animation

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

Discloses that the tool updates the animation in place with live preview, indicating a mutation. However, no annotations are provided, so the description carries the full burden. It does not detail side effects, permissions, or error conditions.

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 efficiently convey the tool's purpose and a key parameter hint. No extraneous information, though the first sentence could be slightly more structured.

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?

Adequately covers the tool's function and parameter meaning given the absence of an output schema and annotations. Missing details about return values or failure modes, but the workflow context is clear via sibling tool references.

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 100%, so the baseline is 3. The description reinforces that 'svg' must be the complete updated SVG, but does not add substantial meaning beyond the schema.

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 states it applies a regenerated SVG to an animation edit request. The verb 'apply' and resource 'edit request' are specific. However, it does not explicitly distinguish from sibling tool apply_patch, which might handle partial updates.

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?

Implies usage after await_edit_request by mentioning 'from await_edit_request'. Provides context for when to use but no explicit when-not or alternative guidance. Lacks exclusion criteria.

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