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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context about the return composition and ordering: the entry pipeline first, then delegate-target pipelines, each with key, name, active revision, delegate blocks, and history. It does not discuss pagination or auth/rate limits, but adds real value beyond 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 a single front-loaded sentence with no filler, leading with the action and resource. It is dense with return-field detail but still structurally efficient.

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 read-only, one-parameter list tool with no output schema, the description usefully explains what is returned: key, name, active revision, delegate blocks, and history. It still omits how the status filter changes results and any pagination behavior, so it is not 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 only parameter, 'status', is fully documented in the schema as live/archived/all with live as default. The description never mentions status filtering, so it adds no parameter meaning beyond what the schema already provides; baseline 3 applies.

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?

States a specific verb and resource: 'List every approval pipeline', and clarifies the scope by distinguishing the entry pipeline from delegate-target pipelines. It does not explicitly differentiate itself from close siblings like get_pipeline or list_pipeline_revisions, so it falls short of a 5.

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?

Provides no explicit when-to-use guidance and does not name alternatives such as get_pipeline or list_pipeline_revisions. The intended use is only implied by 'List every approval pipeline'.

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