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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value on top of that by disclosing the shape of the result (id, name, and which pipeline is default), which matters because there is no output schema. It stops short of describing pagination behavior, so not a 5.

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?

One tight sentence followed by the raw endpoint, with the most important information (what is listed, and what comes back) front-loaded. The trailing 'GET /admin/deal_pipelines' is developer-facing noise rather than agent-helpful content, which keeps it off a 5.

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-required-parameter read-only list tool with full schema coverage and annotations, the description plus structured data is nearly sufficient, and the added return-field summary compensates for the absent output schema. Only pagination/result-count behavior is left unaddressed, a minor gap.

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?

Schema description coverage is 100%: page and per_page are both documented with defaults, ranges and the next_page chaining hint. The description adds nothing beyond the schema about these parameters, so the baseline of 3 applies.

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?

States a specific verb and resource ('List the deal pipelines') and adds useful scope detail: each pipeline has its own stages, and the reply carries id, name and the default flag. It implicitly separates itself from pipelinecrm_list_deal_stages, though it never names that sibling explicitly, so it falls short of a 5.

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 reach for this tool versus pipelinecrm_list_deal_stages or pipelinecrm_deal_totals_by_stage, and no prerequisites or exclusions. Usage is only inferable from the plain 'list' framing, which is the same shape the calibration MID example scored 2 for.

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