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

No annotations are provided, so the description carries the full burden. It discloses the return content (block types, config schema, chaining rules) and its role as a static contract, but does not state that it is a safe read-only lookup, nor any auth requirements or caching 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?

Two short sentences: the first names what the tool returns, the second gives the imperative ordering. No filler, front-loaded with the contract's purpose.

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?

With no output schema, the description must convey return content, and it does by naming the three sections of the contract. It omits the response format (e.g. structured JSON schema vs. prose), a minor gap for a zero-argument tool.

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 takes zero parameters, so the baseline is 4 — no parameter meaning can be lost and the description does not need to compensate for schema gaps. Schema coverage is reported at 100% for an empty object.

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 resource (pipeline schema) and enumerates its contents: valid block types, per-block config schema, and chaining rules. This clearly distinguishes it from the sibling create_pipeline, which consumes rather than exposes this contract.

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?

Explicitly says 'Use before create_pipeline,' which establishes the correct ordering relative to a named sibling. It stops short of stating when-not to use it or naming other alternatives (e.g. list_modules), so it falls short of a full 5.

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