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

Annotations already establish a safe read profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds substantial extra context: the pagination ceiling (default 20, max 50), the meaning and units of the `commercial` figures, and the fact that `commercial` is null for older single-amount deals. It also surfaces a data-safety rule about untrusted CRM content, which is exactly the kind of behavior annotations cannot convey.

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 dual-mode behavior is front-loaded, followed by the commercial-figure breakdown and a security note. The commercial enumeration is dense but earns its place because there is no output schema; only marginal trimming is possible.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly: pipeline list contents, stage/deal structure, and the exact composition and unit convention of the `commercial` object including its null case. An agent has everything needed to call and interpret this tool.

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 only 33%, so the description must compensate, and it does so for pipelineId by explaining the entire behavioral consequence of supplying or omitting it, and for limit by restating default and cap. workspaceId is left to the schema's own description and is not addressed in prose, leaving one parameter slightly under-explained.

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 states a specific verb and resource and spells out the tool's two distinct modes: a list of pipelines (with type and default flag) when pipelineId is absent, and a pipeline's stages plus deals/leads when it is present. It does not name or contrast itself with plausible siblings such as get_pipeline_access or list_records, so it falls short of full sibling differentiation.

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 conditional split ('Without pipelineId... With pipelineId...') gives implicit guidance on how the argument changes behavior, which is useful. However, there is no explicit when-to-use guidance relative to alternatives (e.g. get_pipeline_access, get_deal_commercials) and no statement of when this tool is the wrong choice.

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