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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured fields. The description adds genuine value beyond that by enumerating the returned content — key, name, active revision number, delegating blocks, and history — which matters because there is no output schema. It still omits auth requirements and pagination behavior.

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?

One front-loaded sentence with no filler; the enumeration of returned fields is dense but each item earns its place because no output schema exists to carry them. Slightly long, but 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 list tool with one fully-documented optional parameter and no output schema, the description supplies the domain model and the return shape an agent needs to interpret results. Nothing essential is missing.

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?

Schema coverage is 100% and the single status parameter is fully documented in the schema (live default, archived, all). The description never mentions status, and its phrase "List every approval pipeline" is slightly at odds with the default live-only behavior dictated by the schema. Baseline 3 is appropriate since the schema carries the semantics.

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 states a clear verb and resource ("List every approval pipeline") and goes further by explaining the domain structure: an entry pipeline plus every pipeline reachable via delegate blocks. That is far more specific than a tautology. It does not, however, explicitly separate itself from siblings like get_pipeline or list_pipeline_revisions, so peer differentiation is left implicit.

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?

There is no when-to-use guidance and no named alternative. Nothing tells the agent when to call this versus get_pipeline (single lookup), list_pipeline_revisions, or list_pipeline_uses. The only usage signal is the implicit purpose of a list operation.

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