remove_tag

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Remove an animation tag by name' without mentioning whether removal is permanent, what happens to frames associated with the tag, or how errors (e.g., missing tag) are handled. This is insufficient for a mutating operation.

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?

The description is a single concise sentence that clearly states the operation and the key argument. It contains no fluff, repetition, or unnecessary detail, making it 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 with no output schema, the description covers the essential purpose. It could optionally mention side effects or return behavior, but the combination of a clear description and a well-documented schema makes it sufficiently complete for this low-complexity tool.

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?

The input schema already fully describes the single parameter 'name' as 'Tag name to remove', and the description's 'by name' aligns but adds no extra meaning. With 100% schema description coverage, the baseline of 3 is appropriate; the description does not need to compensate.

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?

The description uses a specific verb 'Remove' with the resource 'animation tag' and the qualifier 'by name', making its purpose unambiguous. It clearly distinguishes itself from sibling tools like create_tag, list_tags, and rename_tag, as it is the only removal operation for tags.

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 description implies the tool is used when you need to delete a tag by name, but it does not explicitly state when to use it vs alternatives or mention any prerequisites (e.g., whether the tag must already exist). No alternatives are named, leaving the usage context only implied.

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