set_frame_comment

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

The description reveals key behaviors: non-persistent session duration, how to clear comments, and the use case. However, with no annotations, it fails to disclose potential overwrite behavior, permissions, or side effects beyond the basic 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 extremely concise: two sentences and a clear note. It is front-loaded with the core action and adds only essential details, wasting no words.

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 tool's simplicity, the description covers the main points: action, persistence, clearing mechanism, and use case. It is complete enough for an agent to understand the tool's function, though parameter details are sparse.

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%, but the description partially explains the 'comment' parameter by noting it can be cleared with an empty string. The 'alias' and 'frame_number' parameters are not described at all, leaving ambiguity for the agent.

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's action: 'Set a comment on a frame for the duration of this session (non-persistent).' It specifies the verb 'set' and the resource 'comment on a frame', making the purpose immediately obvious and distinct from sibling tools.

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 provides clear usage context: 'Useful for annotating frames during forensic analysis.' It also explains how to clear a comment by passing an empty string. However, it does not explicitly state when not to use this tool or mention alternatives.

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