pipedrive_convert_lead_to_deal

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

The description discloses the asynchronous nature, polling mechanism (~30s timeout), and return values (deal ID on success, conversion_id+status on timeout). This adds significant behavioral context beyond annotations (which show readOnlyHint=false). It would be improved by stating what happens to the original lead after conversion.

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 three sentences long, front-loading the primary purpose in the first sentence. It efficiently conveys the asynchronous behavior and timeout handling without extraneous details. Every sentence adds value, achieving high conciseness.

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 lack of an output schema, the description adequately explains return values. It covers the key behavioral aspects (async, polling, timeout). Minor gaps include: the effect on the original lead and the interaction between stage_id and pipeline_id, but overall it is sufficient for action selection.

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?

The schema already provides 100% coverage with clear descriptions for all three parameters (id, stage_id, pipeline_id). The description does not add new semantic information beyond the schema, but no additional elaboration is necessary since the schema is adequate. Baseline score of 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?

The description clearly states the tool's purpose: 'Convert a lead into a deal (Pipedrive v2).' It specifies the verb 'convert' and resource 'lead into deal', and distinguishes from sibling tools like pipedrive_create_deal or pipedrive_get_lead_conversion_status by highlighting the asynchronous polling behavior.

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 usage for converting leads to deals and mentions asynchronous polling and timeout handling. However, it does not explicitly contrast with alternatives like pipedrive_get_lead_conversion_status for manual follow-up or specify when not to use this tool. More guidance on when to choose this over related tools would improve clarity.

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