Respond to Workflow Decision

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

Discloses key behaviors: atomically draining the decision, persisting the outcome, and supporting 'cancel' to abort and restore a snapshot. Does not describe every possible side effect, but the essential behavioral contract is clear.

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 compact and well-structured, with usage conditions clearly separated. Every sentence adds useful information without redundancy.

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?

Provides enough context for an agent to know when to invoke the tool and what the option parameter means. Since no output schema is present, some return behavior is unspecified, but the core usage is 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?

Both parameters have meaningful descriptions that go beyond their names. 'decision' defines what text is expected, and 'option' explains the chosen value plus the special 'cancel' behavior.

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?

Clearly states the tool answers a pending workflow decision and explicitly scopes it to the server's [NEED_INPUT] prompt. It distinguishes itself from set_badge and state tools with explicit do-not-use guidance.

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?

Provides explicit when-to-use and when-not-to-use instructions, including the condition of a pending [NEED_INPUT] prompt and the alternative of using set_badge or a state tool.

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