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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds the underlying REST call (GET /api/v2/deals), which is mildly useful, but says nothing about pagination behaviour, result ordering defaults, or rate limits despite a cursor-based pagination parameter being present.

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 compact sentences with the core purpose front-loaded and no filler. The filter enumeration is somewhat redundant against a 100%-documented schema, which is the only thing keeping this from a 5.

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 11 fully documented optional parameters, a read-only annotation, and no output schema to explain, the description covers what an agent needs to invoke the call. The remaining gap is sibling routing (search_deals vs list_deals), which is a minor omission for a straightforward list operation.

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 11 parameters (including limit bounds and cursor semantics) are already documented in the schema. The description's filter list merely mirrors those field names and adds no syntax, default, or format detail beyond the schema; baseline 3 applies.

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 and resource ('List deals') and enumerates the supported filter axes plus sorting, so the agent knows exactly what the tool returns. It does not, however, differentiate itself from the sibling pipedrive_search_deals, leaving that routing decision to inference.

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?

'Optionally filtered by filter/owner/person/org/pipeline/stage/status and sorted' implies the intended usage pattern, but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to pipedrive_search_deals for text queries. Usage is implied rather than stated.

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