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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds the non-obvious nuance that a same-list call doubles as a claim release, which tempers the destructive framing in that one case. It does not state what a normal move does to the lead's claim, history, or callbacks on the source list, so it adds only partial behavioral context.

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 short sentences, front-loaded with the action and immediately followed by the one case an agent would otherwise get wrong. The trailing endpoint string is marginally useful but not essential prose.

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 3-parameter mutation with no output schema, the description plus annotations cover the essentials: what it does, the destructive and idempotent nature, and the release edge case. Remaining gaps (error conditions, whether a claim is required) are modest.

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%, so both required ids and release_claim are already documented, establishing a baseline of 3. The description earns the extra point by explaining the interaction between release_claim and a same-list destination, which the schema does not capture.

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 uses a specific verb and resource ('Move a lead to another list') and adds the raw endpoint (PATCH /leads/{id}/migrate), so the action is unambiguous. It does not distinguish this from siblings like myphoner_delegate_lead, myphoner_update_lead or myphoner_archive_lead, which also touch lead state.

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?

It gives a genuinely useful conditional: if the destination equals the lead's current list, release_claim=true makes the call a claim release rather than a relocation. That tells the agent when this tool is the right one for de-claiming. It stops short of naming alternatives for the move-vs-update-vs-archive decision.

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