get_pipeline

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 does not disclose behavioral traits like side effects, authentication requirements, rate limits, or error handling (e.g., what happens if the pipeline_id is invalid). It only states 'Get details' without clarifying that it is a read-only operation.

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 very concise at two sentences. It front-loads the purpose and then lists the argument. Every sentence is useful, but it could be slightly more structured (e.g., separate description from args).

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?

Given the tool's simplicity (one required parameter, no output schema), the description is minimally adequate. It tells the agent what the tool does and what input is needed, but it lacks information about the return value structure or any additional context (e.g., how to handle missing pipelines).

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 description coverage is 0%, so the description must compensate. It adds 'The pipeline UUID' to the parameter name, clarifying the required format. However, it does not specify that the parameter is required (though schema marks it) or provide additional constraints.

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 'Get details of a specific pipeline', using a specific verb and resource. This distinguishes it from sibling tools like list_pipelines (retrieve multiple) and create_pipeline (mutate).

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?

No explicit guidance on when to use this tool versus alternatives such as list_pipelines. The context is implied by the tool's purpose, but an agent may benefit from a note that this retrieves a single pipeline by ID, while list_pipelines returns all pipelines.

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