Convert Lead to Estimate or Job

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. It does not mention side effects such as whether the lead status changes, whether this is irreversible, or what the response contains. It only vaguely points to docs, but does not describe the conversion behavior beyond the basic action.

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 two concise sentences, front-loading the purpose and including a direct link to documentation. Every sentence is useful and there is no unnecessary filler.

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 conversion operation with no annotations and no output schema, the description is incomplete. It does not explain what the expected response looks like, what prerequisites exist (e.g., lead must be in convertible state), or any error conditions. The schema and docs link help but the description alone leaves significant gaps.

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 description coverage is 100%, and the schema already explains that `body` is a raw request body matching Housecall Pro docs and that `lead_id` is a lead ID. The tool description adds little beyond the schema, only noting to 'Provide body matching Housecall Pro's convert fields,' which is redundant with the schema. 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?

The description clearly states the tool 'Convert an existing lead into an estimate or a job,' naming the specific action (convert) and resource (lead) and the result (estimate or job). This distinguishes it from sibling tools like create_estimate or create_job, which create from scratch rather than converting an existing lead.

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 provides clear context that this is for existing leads, implying it should be used when you have a lead_id and want to transform it into a quote or work order. It does not explicitly mention when not to use it or name alternatives, but the 'existing lead' context is sufficient to differentiate from creation tools.

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