get_pipeline

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

No annotations are provided, so the description carries the burden. It discloses that the output is automatically stored, returns a formatted preview with an object ID, and can be passed to other functions. It also mentions error messages. This is valuable beyond the schema, though it stops short of stating permissions or explicit read-only safety.

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 moderately sized but contains redundancy; two sentences about using the object ID could be merged. The use of `:param` and `:returns` is conventional, but the instructions are somewhat scattered.

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 one-parameter tool, it covers the return format and how to use the object ID, but it lacks explicit usage guidance versus siblings and does not elaborate on error conditions beyond a generic message. The overall context is adequate for basic use but not comprehensive.

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?

With schema description coverage at 0%, the description must compensate. However, it only restates the parameter name ('The name of the pipeline to fetch') and adds 'unique', which adds little meaning beyond the schema. No format, constraints, or examples are provided.

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 clearly states it 'Fetches information for a specific pipeline' and identifies the resource by the unique `pipeline_name`, distinguishing it from sibling tools like `list_pipelines` (fetching all) and `get_pipeline_version` (a version-specific resource).

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?

It implies usage when you have a specific pipeline name, but does not explicitly mention when to prefer this over alternatives, nor does it state exclusions. The guidance about using object store tools is about post-processing, not tool selection.

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