item_add_flag

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Add a flag', which implies mutation, but does not mention side effects such as whether duplicate flags are allowed, color constraints, or any required permissions. This is a significant gap 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 a single concise, front-loaded sentence that wastes no words. It clearly communicates the action and target without redundancy.

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 the simplicity of the operation, the presence of a full output schema, and complete parameter descriptions, the description is mostly complete. However, it lacks any usage guidance or behavioral details, which prevents a perfect score. The absence of annotation support is partially mitigated by the schema and output schema.

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 schema covers all four parameters with descriptions, including defaults for track_type and track_index. The description adds no extra parameter semantics beyond the schema, so the baseline of 3 applies since the schema does the heavy lifting.

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 action (add a flag), the resource (timeline item), and the color parameter. It distinguishes itself from sibling tools like clip_add_flag by explicitly saying 'timeline item', and from item_get_flags by indicating a write operation.

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 usage on timeline items, which differentiates it from clip_add_flag, but it does not explicitly state when to use this tool vs alternatives. There is no mention of exclusions or prerequisites, so the guidance is minimal but not misleading.

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