bulk_reset_phase

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

No annotations are provided, so the description carries the burden. It discloses the exact behavior: which statuses are reset and that COMPLETED nodes are skipped. However, it does not mention irreversibility, side effects on tasks, error handling for invalid phase names, or whether the operation returns a summary.

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 a single, well-structured sentence that leads with the main action and scope. It includes the key detail about skipping COMPLETED nodes without any superfluous words. Excellent conciseness.

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 only two parameters, no output schema, and no annotations. The description covers the core operation and key edge case (COMPLETED nodes). It could mention return values or whether partial failures are possible, but for its simplicity it is fairly 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?

Schema coverage is 100%, and both parameters already have detailed descriptions in the schema. The tool description adds no significant parameter semantics beyond what the schema already provides, just rephrases includeInProgress as 'optionally IN_PROGRESS'. Baseline of 3 is appropriate.

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 ('Reset'), the target (nodes in a phase), the scope (FAILED and optionally IN_PROGRESS), and the resulting state (PENDING). It clearly distinguishes this bulk operation from sibling tools like reset_task_node by specifying 'in a phase' and the status conditions.

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 implies the use case: reset multiple nodes in a phase rather than individually. However, it does not explicitly compare with alternative tools (e.g., reset_task_node for single-node resets) or state when not to use the tool, such as when only a single node needs resetting.

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