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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavior beyond annotations: it returns summaries only, returns at most 50 items, and avoids loading per-item details. It does not explain cursor pagination behavior or workspace scoping, leaving some behavioral context undisclosed.

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 compact sentence with no wasted words, and the key scoping facts are front-loaded. It efficiently conveys the most important operational constraints.

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?

An output schema exists, so return value structure does not need explanation. Still, for a paginated list tool with optional 'cursor' and 'workspace_id' parameters, the description omits how pagination works and how workspace filtering is applied. It is minimally adequate but leaves important invocation context incomplete.

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 should compensate for the two undocumented parameters. It does not explain 'cursor' or 'workspace_id' at all, beyond the general statement about finding up to 50 pipelines. The parameter names are somewhat self-explanatory, but the description adds no meaningful semantics.

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 gives a specific verb and resource ('Find ... pipelines') and clarifies the scope: summaries only, capped at 50, with no per-item detail loading. This distinguishes it from detail-oriented siblings such as get_pipeline without requiring the agent to inspect their schemas.

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 clearly implies a listing/summary use case and rules out per-item detail loading, which helps separate it from get_pipeline. However, it does not explicitly name get_pipeline as the alternative for detail, so the guidance is clear but not fully prescriptive.

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