Stage Cues Clear

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

Since there are no annotations, the description carries the behavioral burden. It successfully communicates the expected operational feedback to the agent ('Page replies {cleared}') and the non-existence of streaming data ('Emits: nothing'). This is clear operational context.

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 definition is highly concise, utilizing two short sentences to front-load the primary function and the unique identifier, resulting in zero 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?

The definition is highly complete regarding its atomic function: it removes all cues for a given scene, and the agent knows exactly what feedback to expect. The minor deduction is only because it lacks details on failure modes (e.g., scene not found).

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?

With 0% schema description coverage, the description fails to provide meaningful semantic value for the 'scene' parameter. It merely states the action applies 'of the scene' without clarifying prerequisites or the functional necessity of this specific input over others.

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 explicitly states the action ('Remove every waiting cue'), the target ('of the scene'), and the comprehensive nature of the removal ('every waiting cue'). This is highly specific and distinguishes it from tools like stage_cue_remove which likely clear single cues.

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?

It provides a specific operational hint (page command: cues_clear). This tells an AI agent precisely when to prioritize this tool over general cue removal methods or when an external system might be calling it, which is excellent usage context.

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