crm_list_pipelines

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

Beyond the readOnlyHint annotation, the description adds valuable context: required OAuth scope, in-process cache with 300-second TTL, and empty-list semantics. It also explicitly says 'Read-only' reinforcing the safe nature of the call.

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 compact yet information-dense. The first sentence states the purpose, the second gives usage guidance, and the third covers behavioral details. Each sentence earns its place with no filler.

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 simple zero-parameter tool, the description fully covers what the tool returns, when to use it, auth requirements, caching behavior, and edge cases. The existence of an output schema covers return format details, so nothing critical is missing.

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 no parameters, so schema coverage is trivially 100%. The description adds no parameter details because none exist, but the baseline of 4 is appropriate for a zero-parameter tool.

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 opens with a specific verb and resource: 'List every deal pipeline in the account with its stages in display order.' It clearly distinguishes from sibling tools like crm_get_pipeline by indicating it covers all pipelines and includes stage ordering.

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 description explicitly states when to use this tool ('Call this before creating or moving a deal') and explains the necessity for pipeline and dealstage ids. It doesn't explicitly mention alternatives (e.g., crm_get_pipeline for a single pipeline), but the use case is clearly defined, making it a strong 4.

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