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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds useful context those annotations cannot: results are ordered, every account is pre-seeded with a 'Sales' pipeline containing a fixed stage sequence, and the call is free. It stops short of saying anything about size limits or whether aggregate counts are live.

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?

Front-loaded with the returned structure and its ordering, which is the most decision-relevant fact. Every clause carries information (field meanings, default stages, no cost), though the

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?

No output schema exists, so the description carries the burden of describing the return value, and it does so field by field including probability range and outcome enum. It leaves ambiguity about whether deal counts/value are per stage or per pipeline, and says nothing about pagination or size limits for large accounts.

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?

With zero input parameters there is nothing for the schema to document, so the baseline of 4 applies. The description productively uses the space to describe output fields instead of 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?

The description names the specific resource (deal pipelines) and enumerates exactly what comes back: stages in order with id, name, probability, outcome, deal counts and value by currency. It is not a tautology and is distinguishable from crm_save_pipeline / crm_pipeline_report by name, but it never states the listing action or contrasts with those siblings explicitly.

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?

There is no statement of when to call this versus crm_pipeline_report, crm_list_segments, or the pipeline mutation tools. The only inferable guidance is that it is a read operation, and nothing tells the agent it should call this before crm_move_deal or crm_save_deal to discover valid stage ids.

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