Stage Timeline Show

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

Since there are no annotations, the description takes full responsibility. It successfully discloses highly specific behavioral traits, such as the exact physical placement of the timeline bar and the expected page reply response ('{shown}').

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 two sentences are highly efficient, providing maximal information density with zero fluff. The structure effectively separates the activation/placement context from the alternative command and expected output.

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 description is complete for this specific function. It addresses *what* the tool does, *how* it appears physically, and *how* the system will react, leaving no critical functional detail unaddressed for the AI agent.

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 must carry the load. It clearly defines the function of the 'scene' parameter as the context for the placement and the 'show' parameter by explaining its toggle action (show/hide).

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 is exceptionally clear, using specific language like 'Show the timeline bar' and detailing its physical location relative to the person (0.6 m ahead, 30 cm below the eyes).

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 useful parallel guideline by stating that hiding the bar is equivalent to the 'page command: timeline.' However, it doesn't offer guidance on when this tool is needed compared to other visual state-management siblings.

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