list_pipelines

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

With no annotations, the description carries the full burden. It transparently indicates a read-only listing behavior ('List all') and specifies the output fields ('pipeline name, stage names, and lead counts'), setting expectations for return content without hidden side effects.

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 concise sentences with a useful example, front-loaded with the primary action and outcome. Every word adds value, and the structure is clear and direct.

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 tool with no output schema, the description sufficiently covers what the tool returns and the scope. It mentions all pipelines, stages, and lead counts, providing enough context for an agent to select and use the tool correctly.

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 has zero parameters, and the baseline for 0 params is 4. The description doesn't need to explain parameter details because there are none, and the schema already confirms this with 100% coverage.

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 the tool lists all sales pipelines with their stages, using the specific verb 'List' and resource 'sales pipelines.' It also distinguishes from siblings like list_task_statuses and get_pipeline_leads by focusing on pipeline and stage names.

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?

The example user intents ('Show my pipelines' or 'What stages does my sales pipeline have?') provide clear context for when to use the tool. It does not explicitly mention alternatives or exclusions, but the examples effectively convey appropriate usage scenarios.

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