pipedrive_my_open_deals

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

No annotations are provided, so the description carries the burden. 'List' and 'open deals' imply a read-only, filtered query, and the sort order ('most recently updated') is disclosed, but there is no mention of pagination behavior, what 'open' excludes, or permission/auth needs beyond the as_user note.

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, front-loaded with the core scope before the ordering detail. No waste.

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 simple list tool with no output schema and no annotations, the description covers scope and ordering but omits what fields are returned and how pagination is expected to be used, which the agent must infer from the schema.

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 100% with all four parameters documented in the schema itself. The description only gestures at as_user via '(or as_user)' and adds nothing about pipeline_id or cursoring beyond what the schema already says, so baseline 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?

States a specific verb (List), resource (open deals), and scope (owned by current user or as_user), plus ordering. It implicitly separates itself from pipedrive_deals_list by the 'owned by current user' restriction, though it never names that sibling to sharpen the distinction.

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 implied: call this when you want the caller's own open deals rather than all deals. There is no explicit when-to-use/when-not guidance and no reference to pipedrive_deals_list or pipedrive_deals_search as alternatives.

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