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

Annotations only carry destructiveHint=true; the description adds material context beyond that by labeling it a WRITE with no API undo and stating the conversion cannot be reversed. It also discloses the return payload (UUID and link), though it omits side effects on the source lead and any permission requirements.

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?

Front-loads the most decision-relevant fact ('WRITE (no API undo)') and packs purpose, irreversibility, and return value into two tight sentences with no 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?

With no output schema, the description usefully names what is returned (UUID and link) and flags the irreversible mutation, which is the key risk. It stops short of noting lead-state side effects or auth/permission needs, but is otherwise sufficient for a one-parameter tool.

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% for the single required UUID parameter, so the schema documents the input fully. The description adds no format or constraint detail beyond that, making the baseline 3 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 and resource ('convert a lead into a job') and clarifies the mechanism ('creates a new job from the lead'), which distinguishes it from siblings like workiz_create_job and workiz_create_lead without opening their schemas.

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 the use case (you have an existing lead you want to promote), but it never explicitly states when to use this over workiz_create_job or workiz_activate_lead, nor any prerequisites such as the lead needing a particular status.

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