pipedrive_product_deals_list

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read operation, but the description says nothing about pagination (cursor), default page size, permissions, or return shape. The schema covers defaults, yet the description adds no behavioral context of its own.

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?

A single efficient sentence with the core action and its main qualifier front-loaded. No filler, though it is arguably too sparse for a tool with pagination semantics.

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 read-only list tool with complete parameter documentation but no annotations and no output schema, the description is adequate but thin. Pagination behavior and the cursor workflow are left entirely to the schema, and there is no indication of what a deal record contains.

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 four parameters (limit, cursor, status, product_id) are already documented in the schema. The description only restates the optional status filter, adding nothing beyond what the schema provides. 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 ('List') and resource ('deals a product is attached to') with a clear scope note about optional status filtering. It is distinguishable from the inverse sibling pipedrive_deal_products_list (which lists products for a deal), though it never names that 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?

The phrase 'optionally filtered by status' implies intended usage but gives no explicit when-to-use context, no exclusions, and no routing to alternatives such as pipedrive_deals_list or pipedrive_deal_products_list. Minimal implicit guidance only.

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