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 one genuinely useful behavioral fact not in the schema — that money values return as decimal strings — plus the underlying endpoint (GET /deals), but says nothing about pagination behavior or result shape, so it is a modest add over the annotations.

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?

Two sentences, front-loaded with the core purpose before the filter inventory. The field enumeration is somewhat dense but each sentence carries distinct information and there is no filler.

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 20-parameter list tool with no output schema, the description covers scope, filtering surface and the one non-obvious return detail (decimal-string money). It omits anything about total counts or pagination semantics, but pagination parameters are self-documented in the schema, leaving only minor gaps.

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%, so all 20 parameters are already documented with formats, ranges and cross-references. The description restates the filterable dimensions at a high level ('value range', 'created, expected-close, closed or modified dates') without adding syntax or defaults beyond the schema, which is the baseline 3 case.

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+resource ('List or search deals') and enumerates the dimensions returned and filterable, so an agent can tell it apart from pipelinecrm_get_deal (single record). It never names a sibling alternative such as pipelinecrm_deal_totals_by_stage, so differentiation is implicit rather than explicit.

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?

Usage is implied by the filter list (search when you need a filtered set), but there is no explicit when-to-use guidance, no exclusions, and no routing to alternatives like the aggregate totals tool or the single-deal getter.

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