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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by naming the concrete data fields a deal carries and disclosing the raw GET /deals endpoint, but says nothing about pagination behavior, result volume, or whether includes triggers extra cost beyond the schema's note.

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 tight sentences, front-loaded with the resource and its payload, then filters, then ordering. Nothing is redundant, though the parenthetical state enumeration duplicates the schema enum and could be trimmed.

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 9 all-optional params, 100% schema coverage, and no output schema, the description's field enumeration helpfully substitutes for the missing return contract. It is close to complete for an agent to call it correctly; only the relationship to search_deals remains unstated.

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 every parameter is already documented, making 3 the baseline. The description does mirror the filter dimensions (company, user, pipeline, state) and ordering dimensions, which aids recall, but it omits includes, page, and perpage entirely and adds no format or interaction detail beyond the schema.

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 deals') and enumerates the notable fields returned (value, state, pipeline/stage ids, target date), plus the endpoint. It distinguishes itself from get_deal and create_deal implicitly by being a collection query, but never names search_deals or get_deal_stats as the contrasting siblings an agent should weigh.

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 phrase 'Filter by company, responsible user, pipeline or state; order by...' conveys the intended usage pattern, but it is purely descriptive of capability rather than prescriptive about when to choose this over search_deals or get_deal_stats. No exclusions or prerequisite notes are given.

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