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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real scope detail beyond that — archived deals are excluded and won/lost deals are included alongside open ones — but says nothing about volume limits, pagination, or ordering, which matter for a listing call.

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?

It is a single sentence with no wasted clauses, and the core scope (unarchived, one company, all statuses) is front-loaded. The trailing 'open_deal_count is the open ones' is slightly awkward phrasing but does convey a useful return-field hint.

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 one-parameter read-only listing tool with no output schema, this is close to complete: it says which deals come back, which statuses are included, what each item contains, and hints at an aggregate field. The only gap is not naming cardId, which the company-scoping phrase largely covers.

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 0% and the single nested parameter cardId is never named, yet the phrase 'on one pipeline company' effectively tells the agent the parameter identifies a company. That is useful inference but not explicit, so it adds only partial meaning over the bare uuid-typed field.

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 gives a specific verb and resource ('Lists every unarchived deal') plus scope ('on one pipeline company'), and clarifies the status set (open, won, lost) and that each item carries its deal summary. That distinguishes it reasonably from listDeals and getDealSummaries, though it never names a sibling explicitly.

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 only implied: an agent can infer this is the per-company deal listing versus the broader listDeals or listDealCandidates, but the description states no when-to-use condition, no exclusions, and no prerequisites. Nothing misleads, but nothing routes the agent either.

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