List SDLC pipeline phases

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

The description discloses that the tool is read-only and idempotent, matching annotations. It also adds context that it returns only the skeleton and to read source_uri for details, which is beyond what annotations provide. No contradiction with annotations.

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 three sentences, each serving a purpose: stating what it does, when to use it, and what it returns. No fluff, front-loaded with the core action. Every sentence earns its place.

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 the tool has no parameters, a clear output schema, and annotations covering safety, the description fully covers purpose, usage, and limitations. It explains the skeletal output and directs to source_uri for details, leaving no information gap for an AI agent.

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?

There are no parameters and schema coverage is 100%. The description reinforces that it takes no arguments. Baseline for 0 parameters is 4, and the description adds no additional parameter info but confirms the lack of arguments.

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 it lists SDLC pipeline phases with specific details (execution order, skip conditions, judgment gates). The verb 'list' and resource 'phases' are explicit, and it distinguishes from siblings which are unrelated tools like get_document or list_presets.

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 states when to use: to drive the SDLC flow in a host that cannot run the plugin, or to answer what happens when. It doesn't mention when not to use, but this is a simple read-only list tool with no alternatives among siblings, so the guidance is sufficient.

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