validate_current_clip

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

No annotations are provided, so the description bears full responsibility. 'Check' is vague; it does not disclose what validation entails, whether it modifies state, requires permissions, or has side effects. Minimal transparency.

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?

Single sentence is very concise and front-loaded with the main action. Could benefit from a slightly more structured format (e.g., purpose and behavior separated), but no wasted 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 has an output schema (from context signals), the description does not need to explain return values. However, it lacks detail about the nature and scope of the validation (e.g., what criteria are checked). Adequate but not complete.

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?

Tool has zero parameters, so schema coverage is 100% by default. Description adds no parameter information, which is acceptable because there are none to describe. Baseline is high due to trivial parameter count.

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?

Description 'Check the timeline clip under the playhead' uses a specific verb ('check') and resource ('timeline clip'), and the location 'under the playhead' distinguishes it from sibling tools like `inspect_clip` (which likely inspects properties) and `run_full_validation` (broader scope).

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?

Description implies usage when you need to validate the clip at the playhead, but provides no explicit guidance on when not to use it, nor alternatives like `inspect_clip` or `run_full_validation`. Usage is only implied.

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