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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by defining the pipeline concept and exposing that this is a GET endpoint, but it does not discuss error behavior, authentication, or response shape.

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 two short sentences with zero waste. The core purpose and resource definition are front-loaded, followed by the endpoint for technical clarity.

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 read tool with annotations and full schema coverage, the description provides enough context to select and invoke it correctly. It is slightly incomplete only because it does not mention return shape or error conditions, though those are less critical for a basic getter.

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 100%, and the single pipeline_id parameter is already documented in the schema as 'CATS pipeline id.' The description reinforces that lookup is by id but adds no additional format, validation, or semantic detail beyond the schema.

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 specific verb and resource: get one pipeline by id. It also clarifies that a pipeline is a candidate on a job and includes the underlying endpoint GET /pipelines/{id}, which clearly distinguishes it from list/filter pipeline siblings.

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?

Usage is implied by the phrase 'by id' and the contrast with list/filter siblings, but the description does not explicitly say when to use this tool versus cats_list_pipelines, cats_filter_pipelines, or cats_get_pipeline_status_history. No exclusions or alternatives are named.

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