pipedrive_get_deal_conversion_status

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

Goes well beyond annotations by detailing the status contract (completed/failed/rejected/not_started/running), purging behavior (404 signals terminal), and that only 'completed' carries lead_id. Also warns against unbounded loops. Annotations already indicate readOnly and idempotent, but description adds critical polling logic.

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?

Description is comprehensive yet concise, with each sentence serving a distinct purpose: purpose, status contract, purge behavior, polling advice. No redundant information.

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?

Given the complexity of an async polling tool, the description covers all critical aspects: status meanings, terminal states, edge case of purge, and polling strategy. No output schema, but description clarifies output expectations (lead_id only on 'completed'). Exceptionally complete.

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% and description adds context: 'id' is the deal that was converted, 'conversion_id' is the job UUID from the convert call. This helps the agent understand the origin of parameters beyond type definitions.

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?

Clearly states it gets the status of a deal-to-lead conversion job, specifying the resource (conversion job) and action (get status). However, it does not explicitly distinguish from the sibling tool pipedrive_get_lead_conversion_status, which likely covers the reverse direction.

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?

Provides explicit guidance on when to poll (after conversion call) and when to stop (terminal statuses or 404 after prior valid status). Advises bounded poll budget. Lacks explicit comparison to alternatives but effectively tells when to use and when not to poll indefinitely.

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