stop_clip_slot

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

No annotations exist, so the description must disclose behavior. It only says 'Stop a clip slot.' It does not mention whether it resets the clip position, if the slot needs to be playing, what happens if the slot is empty, or any side effects. This is insufficient for safe invocation.

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 (4 words), but this brevity sacrifices necessary information. It is front-loaded with the action, but the lack of detail makes it insufficient for a tool with two required parameters and many siblings. Adequate only if the tool is trivially simple, which it is not.

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?

The tool has two required parameters, no annotations, and the description provides no parameter info, usage context, or behavioral details. Even though an output schema exists, the description remains incomplete. An agent would need to guess or rely on external knowledge to use it correctly.

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%: the description does not explain 'track_index' or 'clip_index' at all. The schema only gives titles and types. With no parameter descriptions, the agent lacks any semantic context for the integer values (e.g., zero-indexed? range?). Description must compensate but fails completely.

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 uses a specific verb ('stop') and resource ('clip slot'), clearly distinguishing it from sibling tools like 'fire_clip_slot' (fires) and 'stop_clip' (stops a clip, but not necessarily a slot). However, it does not explain what a 'clip slot' is, which may be ambiguous for new users.

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 over alternatives such as 'stop_clip', 'stop_all_clips', or 'stop_track_clips'. There are no when-to-use or when-not-to-use statements, forcing the agent to infer context from the name alone.

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