deals_convert_status

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

Discloses statuses and output lead_id on completion. No annotations, so description carries burden; it adequately describes that it is a polling operation without side effects, but could mention it's read-only.

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?

Three sentences, front-loaded with purpose, efficient use of words. No redundancy.

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?

No output schema, but description explains possible statuses and successful response includes lead_id. Covers main behavior; minor missing details on errors.

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 already provides clear descriptions for both parameters (100% coverage). Description adds no new semantic information beyond restating usage.

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 the tool checks status of a deal-to-lead conversion job. Distinguishes from sibling deals_convert_to_lead (starts conversion) and leads_convert_status (lead-to-deal).

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 instruction to use conversion_id from deals_convert_to_lead and lists statuses. Lacks explicit when-not-to-use or alternatives, but context makes it clear.

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