listStages

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'List all pipeline stages', which conveys a read-only intent but does not mention ordering, pagination, authentication requirements, or whether archived stages are included. This is minimal additional value beyond the tool name.

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 no wasted words. It is front-loaded with the action and resource, making it immediately clear what the tool does.

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 is simple (no params, no output schema, no annotations), so the description is minimally adequate. However, it lacks context about the scope of 'all' (global across pipelines), whether pagination exists, or what the return structure looks like. Given the absence of an output schema, the description could have provided more behavioral context to be fully 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?

The tool has no parameters, and the schema is empty with 100% coverage. Per the rubric, 0 params corresponds to a baseline of 4. The description adds no parameter information, which is appropriate since none exist. No confusion is introduced.

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 'List all pipeline stages' clearly states the verb (List) and resource (pipeline stages). It distinguishes from siblings like getStage (singular) and listPipelines (pipelines, not stages). Minor ambiguity remains about whether 'all' means globally or within a specific pipeline, but with no parameters, the global scope is implied.

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 usage for retrieving a list of all stages, but provides no explicit context on when to use this tool versus alternatives (e.g., getStage for a specific stage, createStage/updateStage for modifications). No when-to-use or when-not-to-use guidance is given.

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