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

No annotations are provided, so the description must disclose behavioral traits. It mentions returns all open+closed deals and fields, but does not disclose pagination behavior (limit/offset), default ordering, or potential performance implications. It also doesn't mention whether it returns only summarized fields or full objects. Given zero annotation coverage, this is a significant gap.

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 description is concise (two sentences) and front-loads the core purpose: 'List deals.' It then adds return fields and use cases efficiently. No filler, but it could be slightly more explicit about pagination. Still, it's well-structured.

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?

The tool is relatively simple (list, no output schema), but with no annotations and 50% schema coverage, the description should cover more. It misses pagination details (limit/offset behavior), ordering, and any potential performance hints. For a list tool, it's adequate but not complete for an agent to understand all invocation nuances.

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 50%: the schema describes 'search' and 'stageId' but not 'limit' and 'offset'. The description does not explain limit/offset semantics, which are likely standard pagination but still undocumented. It adds minimal value beyond the schema; the 'filter by stage' hint reinforces stageId but doesn't clarify limit/offset, so a 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?

The description clearly states it lists deals and specifies the fields returned (stage, value, contact, company). It differentiates from sibling tools like deals_get (which retrieves a single deal) and deals_create/update/delete. However, it doesn't explicitly name those siblings, but the verb 'list' and resource 'deals' are specific enough.

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 description provides clear use cases: 'summarize pipeline, find a deal to update, or filter by stage / value.' It does not explicitly mention when not to use it or contrast with alternatives, but the context is sufficient. The mention of 'filter by stage / value' implies the stageId and search parameters, which is helpful.

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