conduyt_list_pipelines

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

No annotations and no output schema, so the description carries the full burden. 'List' implies a read-only operation and the phrase 'with their stages' discloses the nested return structure, which is useful. It says nothing about permissions, pagination, ordering, or whether all pipelines are returned (archived included), leaving meaningful gaps.

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?

Two short sentences with zero padding. The resource-and-scope statement comes first, followed immediately by the actionable usage guidance.

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 zero-parameter read tool with no output schema, the description covers purpose, rough return contents, and the motivating use case. Only minor gaps remain (no mention of pagination or archived pipelines), which are unlikely to cause misinvocation.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no filtering inputs are needed to obtain the full pipeline list.

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 verb and resource ('List all sales pipelines with their stages') and even hints at the return shape (pipelines with nested stages). It distinguishes itself from the create/update/delete pipeline siblings by describing a discovery role, though it doesn't name a specific sibling alternative.

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?

Explicitly says when to use it: 'to discover pipeline and stage UUIDs before creating or moving deals.' That gives a concrete precondition and routes the agent correctly, but it doesn't call out any exclusions or name a sibling alternative by name.

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