list_pipelines

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

Describes returned fields (id, name, milestones sorted), notes rarity of changes, and implies read operation. However, does not mention pagination behavior despite pagination parameters in schema, and lacks details on rate limits or other 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?

Three sentences with front-loaded main action and no redundancy. Each sentence adds value: what it does, how to use it, and caching advice.

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 pagination parameters, description lacks explanation of pagination behavior (e.g., total count, paging info). For a listing tool, this omission reduces completeness for correct invocation.

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?

Input schema has 2 parameters (page, perPage) with 0% coverage in schema descriptions. The description does not explain these parameters at all, leaving the agent without guidance on their usage or defaults.

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?

Clearly states it lists sales pipelines from Capsule CRM and returns id, name, and milestones. Distinguishes from siblings by specifying its role in opportunity creation and use with list_milestones.

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 advises when to use: to discover pipelineId for creating an opportunity, then pick a milestone via list_milestones. Recommends caching due to stability, providing clear context for usage.

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