list_phases

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

No annotations are provided, so the description carries the burden. It explains that phases are a navigational frame, not the structural spine, which adds context about the tool's conceptual role. However, it does not disclose if there are any side effects, read-only nature, or other behavioral traits beyond the listing.

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 consists of two concise sentences. The first sentence immediately states the tool's purpose. The second sentence provides additional conceptual context. Every sentence is valuable, and there is no waste.

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 the tool has no parameters and an output schema exists (though not provided), the description adequately specifies the number of phases (seven) and their range. The conceptual note adds context that helps an agent understand the output's nature. The description is complete for this simple list tool.

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 tool has zero parameters, so schema description coverage is 100%. The description adds no parameter information but provides useful context about the phases' role, which adds value beyond the empty schema. Baseline for zero params is 4.

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 lists the seven phases of the strategic sourcing process, specifying the range Phase 0 through 6. This is a specific verb and resource, and it differentiates from sibling 'get_phase' which likely retrieves a single phase.

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 does not explicitly guide when to use this tool versus alternatives. It implies listing all phases, but no when-not or alternative comparison is provided. Sibling tools like 'get_phase' exist, but no guidance is given.

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