get_pipeline

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get a pipeline run,' with no mention of return behavior, error conditions, or whether the run is current/historical. The read-only nature is implied by 'get,' but no additional context is given.

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 short sentence with no wasted words. However, it is under-specified rather than appropriately concise; it trades value for brevity. Given the simplicity, this is acceptable but not excellent.

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 single-ID retrieval with an output schema, the description is minimal but functional. It fails to mention the relationship to pipeline_id or any selection criteria, but the schema and resource name cover the basics. With sibling tools, the purpose is distinguishable.

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 single parameter pipeline_id is not mentioned in the description. Schema description coverage is 0%, so the description should compensate, but it does not. While the parameter name is somewhat self-explanatory, the description adds no guidance on its meaning or format.

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 uses the specific verb 'get' with the resource 'pipeline run', clearly identifying the tool's function. It distinguishes from sibling tools like get_pipeline_steps and get_pipeline_step_log, though it doesn't explicitly contrast with get_pipelines.

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 guidance on when to use this tool versus get_pipelines or get_pipeline_steps. The description only states what it does, not when to invoke it, leaving the agent to infer usage from the resource name.

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