remove_anim_curve_name

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is well covered. The description adds a useful Returns field list (removed, already_absent, present, curve_count, saved) that reveals the idempotent outcome shape and that the asset is saved, which is valuable given no output schema. The 'idempotent' restatement slightly duplicates the annotation.

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 tight elements: purpose first, then a returns breakdown. Front-loaded and waste-free, though the inline 'idempotent' slightly duplicates the annotation.

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 two-parameter removal tool with no output schema, the description covers purpose, idempotent behavior, and the return shape. Safety is covered by annotations. Only minor gaps (no prerequisites/alternatives) remain.

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% with both parameters required and documented, so the schema carries the parameter semantics. The description only restates 'curve name' conceptually and adds no format or edge-case detail 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?

States a specific verb (Remove) and resource (a curve metadata entry / curve name on a USkeleton), which distinguishes it from the sibling remove_anim_curve that removes actual curve data. It does not explicitly name a sibling, but the 'metadata entry (curve name)' phrasing carves out its scope clearly.

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?

The narrow purpose implies when to use it, but the description gives no explicit when/when-not guidance and does not point to alternatives (e.g. rename_anim_curve, remove_anim_curve). The agent must infer selection from the name alone.

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