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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds value beyond the annotations by noting that the reply's meta names the default pipeline, which an agent could not infer from structured fields. It doesn't discuss pagination behavior, keeping it from 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?

Three terse sentences, front-loaded with the core purpose and actionable follow-up. The trailing 'Teamleader: dealPipelines.list.' is a minor API-reference flourish but costs almost nothing.

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 read-only list tool with full annotation coverage, good parameter documentation, and no output schema, the description is nearly complete—it even explains the default-pipeline meta detail. Adequate to call correctly; only pagination semantics are unaddressed.

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 coverage is 75%, with page, page_size, and term documented; only the status enum lacks a description. The description adds no meaning beyond the schema, so the high-coverage baseline of 3 is appropriate.

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 sales pipelines') and distinguishes usefully from the sibling list_deal_phases by explaining how the pipeline id feeds that tool. An agent can tell exactly what this returns and how it differs from related listing 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 tells the agent to use a returned pipeline id with teamleader_list_deal_phases, giving a clear downstream use case. It stops short of explicit when-not conditions or alternatives for listing itself, so a 4 rather than a 5.

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