set_tag

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

Since no annotations are provided, the description must carry the behavioral disclosure. It says 'create or update' but does not explain the behavior when updating (e.g., does it replace existing tags, merge, or fail if no tag exists?). No mention of side effects, prerequisites, or return values, which is insufficient for a 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?

The description is only one sentence, but it is under-specified rather than concise. It omits essential context, so brevity here is not a virtue; it fails to convey enough information. A concise description would still include necessary guidance.

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 tool with five parameters, no output schema, and no annotations, the description is inadequate. It does not explain what an animation tag is, how the parameters interact, or what the expected result is. The tool's complexity is not matched by the description, which would leave the agent without enough information to call it correctly.

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 0%, and the description does not elaborate on what the parameters (name, filename, from_frame, to_frame, direction) represent or how they relate to the tag. The description adds no meaning beyond the schema's raw field names, leaving the agent without semantic guidance for these five 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?

The description identifies a specific action ('Create or update') on a specific resource ('an animation tag'), which is clear enough to understand the core function. However, it does not distinguish it from sibling tools like delete_tag or export_tag, though those are clearly different operations, so it does not fully differentiate among siblings.

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 regarding creating versus updating, nor any mention of alternatives or exclusions. The description simply states the action without context, leaving the agent to infer usage from the name and parameters.

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