add_tag

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

With no annotations, the description carries full burden for behavioral disclosure. It explains the direction and color parameters but omits important details: what happens if a tag with the same name exists, if from_frame > to_frame, or any side effects. The basic creation behavior is implied, but not comprehensive.

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?

Extremely concise: two sentences. First sentence states purpose and frame range. Second sentence lists optional parameters. No redundant information. Well-structured for quick parsing.

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?

Given 6 parameters (4 required), no output schema, and no annotations, the description is incomplete. It covers direction and color but omits filename, name, from_frame, to_frame details (though from/to are partially addressed). It does not describe return value or what the tag represents in animation context.

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 coverage is 0%, so description must compensate. It explains 'direction' (enum values) and 'color' (optional, timeline display). It clarifies 'from_frame' and 'to_frame' as frame range with 1-based indexing. However, 'filename' and 'name' are not explained; their purpose is somewhat obvious but not formally defined.

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 clearly states the tool creates an animation tag spanning frames, with specific verb 'create' and resource 'tag'. It distinguishes from sibling tools like set_tag or remove_tag by focusing on creation, though not explicitly comparing.

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 use this tool vs alternatives like set_tag or remove_tag. The description does not mention any prerequisites, conflicts, or context for when this is appropriate.

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