List Pipelines

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

Description notes the tool takes no arguments and returns specific fields (id, name for pipelines; id, name, win_probability for stages). Being a listing operation with no side effects, this provides sufficient behavioral transparency despite no annotations.

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 sentences succinctly cover purpose, usage context, and output structure with no unnecessary words. Perfectly front-loaded.

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?

Given no output schema and simple return, the description fully explains the output structure and why the tool is useful (mapping names to IDs). No gaps.

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?

No parameters in schema, so description does not need to add parameter semantics. Baseline score of 4 applies as per guidelines for 0 parameters.

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?

Description clearly states the tool lists every sales pipeline with ordered stages, uses specific verb 'list' and resource 'pipelines', and distinguishes from siblings by noting its use for mapping names to IDs needed by other tools.

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 states when to call this tool first for mapping human pipeline/stage names to numeric IDs used by sibling tools. Though no explicit when-not-to-use, the use case is clear.

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