Stage Gesture Reset

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

With no annotations provided, the description must carry the full weight of operational context. It explains that the tool reverts state to a default/engine baseline and specifies the logical boundaries of the reset ('person's own map' or 'this scene's rows').

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 dense but highly efficient. It manages to pack the core function, the conditional logic of operation (one vs all intents), and the scoping of the change into one tightly structured sentence.

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 that no annotations or detailed schema descriptions exist, the description provides all necessary operational context. It tells the agent exactly *how* and *where* the reset occurs, making it functionally complete for selection.

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?

Since schema description coverage is 0%, the description is critical. It provides excellent semantic meaning for the 'owner' parameter, clarifying that it dictates whether the reset applies to the user's global map or the current scene's rows.

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 clearly states the tool resets the 'engine's gesture.' It is specific enough to identify the function but relies slightly on the user understanding what 'engine' refers to in this context.

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 explicitly details the two primary modes of operation: resetting 'for one intent' versus 'for every intent with no intent given.' It also defines the scope distinction (person's map vs. scene's rows).

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