pipedrive_my_open_deals

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

With no annotations, the description carries the burden. It mentions sorting by most recently updated, which is helpful. However, it does not disclose pagination behavior (despite cursor and limit parameters), any rate limits, or permissions required.

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 a single concise sentence with no wasted words. It front-loads the core function and sorting behavior.

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 list tool without output schema, the description covers the main purpose (listing open deals by owner) and sorting. However, it lacks details on pagination (cursor/limit) and what fields are returned, which are typical expectations.

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 documentation coverage is 0%. The description only implicitly references 'as_user' via parentheses but does not explain pipeline_id, cursor, or limit. An agent cannot infer their purpose from the description alone.

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 the tool lists open deals owned by the current user (or specified user via as_user). It uses a specific verb-resource pair and implies distinction from sibling tools like pipedrive_deals_list (which likely returns all deals) and pipedrive_deals_search.

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 implies the tool is for listing own open deals but does not explicitly state when to use it over alternatives. No mention of when not to use or what other tools exist for different scopes (e.g., all deals or search).

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