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

With no annotations, the description carries the full burden; 'Read-only' is the single most important disclosure for this tool and it is made clearly. It does not cover failure behavior for a missing id, permission requirements, or whether the default flag has side effects, so the disclosure is thin beyond the read-only statement.

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?

Front-loaded with the access pattern, then the return fields, then the safety note; no filler. The phrasing 'One pipeline by id' is slightly elliptical but readable.

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 one-parameter, non-destructive read with no output schema, the description gives the lookup key, the projected fields, and the read-only nature. Only error/permission behavior is absent, which is a minor gap at this complexity level.

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 coverage is 100% and the schema already documents the single 'id' parameter as a UUID. The description's 'by id' adds nothing beyond that, so the baseline of 3 for fully-documented parameters applies.

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 retrieval action ('One pipeline by id') and enumerates the returned shape (id, name, is_default), which separates it from crm_list_branches and crm_list_all_branches by implying single-record lookup. It stops short of naming those siblings explicitly, and the branch/pipeline terminology swap between name and description adds minor friction.

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?

'By id' implies the precondition of already holding a pipeline id, which is sufficient context to pick this over the list tools. There is no explicit when-to-use statement, no exclusion of alternatives, and no note on what happens if the id is unknown.

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