get_clip_at_playhead

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

With no annotations provided, the description carries the full burden of disclosing behavior. It merely restates the operation name without explaining what happens when no clip is at the playhead, what the return value is, or any side effects. 'Expanded operation' is vague and adds no real behavioral detail.

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, short sentence with no waste, so it is concise. However, it does not front-load any useful information beyond what the name already conveys, making it minimally valuable as a description.

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 getter with no parameters and no output schema, a terse description might be acceptable, but the tool has a close sibling ('get_clip_at_position') and no indication of what 'playhead' specifically refers to or how the result differs. Important context about return format and edge cases is missing.

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 tool has zero parameters and the empty schema documents this completely (coverage 100%). Per calibration, a tool with no parameters receives a baseline of 4, and the description adds no unnecessary parameter information.

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 states the action 'get clip at playhead' with a clear verb and resource. However, it does not distinguish itself from the closely named sibling 'get_clip_at_position', so there is no differentiation from similar 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 offers no guidance on when to use this tool versus alternatives such as 'get_clip_at_position', 'get_selected_clips', or other timeline inspection tools. No exclusions or preferred contexts are mentioned.

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