delete-phase

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

The description mentions that deletion archives the phase in Float, which is a key behavioral trait beyond a simple delete. However, it does not disclose side effects, authorization requirements, or whether the operation is irreversible, which are important for a destructive action.

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 sentence that conveys the core purpose. It is not verbose, but could include more essential information (e.g., side effects) without losing 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?

For a destructive tool with no annotations or output schema, the description is incomplete. It omits important context such as whether the deletion is reversible, any constraints on the phase (e.g., cannot delete if it has tasks), and who can perform the operation.

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?

The schema already fully describes the single parameter 'phase_id' (100% coverage), and the description adds no additional meaning beyond what the schema provides. Thus, baseline score 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 clearly states the action ('Delete') and the resource ('phase'), and adds the context that it archives the phase in Float. This distinguishes it from sibling tools like create-phase, update-phase, and list-phases.

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 lacks any guidance on when to use this tool vs. alternatives, prerequisites (e.g., phase must exist, no active tasks), or when not to use it. No alternatives or context for invocation are provided.

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