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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'List' clearly indicates a read-only, non-destructive operation, and the mention of 'what each is for' sets expectations for informational output. No auth or side-effect concerns are plausible for a zero-parameter listing, so the description is adequately transparent.

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 concise sentence with the action verb and resource front-loaded, followed by the explicit phase names and the purpose of the output. Every word earns its place, and there is no redundancy or filler.

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 simple, zero-parameter, informational list tool, the description fully covers what the tool does and what the response will convey. No output schema or annotations exist, but none are needed at this level of complexity; an agent can confidently invoke this tool based solely on the description.

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 input schema has zero parameters, so the description does not need to document parameter semantics. It still adds meaningful context about the phases being listed, which helps an agent understand the tool's purpose even without parameters.

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 names a specific resource ('lifecycle phases this server serves') and enumerates the phases (setup, modify), plus explains that each phase's purpose is included. This clearly distinguishes it from sibling tools like list_operations and list_providers, which target different resources.

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 use when an agent needs to understand the server's lifecycle phases, but it does not explicitly state when to choose this tool over alternatives or mention any exclusions. The context is clear enough for an agent to infer, but no explicit guidance is given.

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