undo_lead_transition

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

There are no annotations provided, so the description carries the full burden for behavioral disclosure. It states the operation is an undo of a recent transition, but does not disclose side effects, whether the transition is actually removed or reverted, permission requirements, or behavior when no recent transition exists. This is minimal for a mutation tool.

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 sentences plus a parameter list, with no filler. The purpose is stated first, and the parameter explanations are concise. However, it is quite terse and could benefit from a bit more context without becoming verbose.

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 2-parameter mutation tool with no annotations, the description omits important details such as what constitutes a 'recent' transition, whether the operation is reversible, and what the output schema represents. It describes the operation at a high level but leaves key operational questions unanswered.

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 input schema has no descriptions (coverage 0%), so the description's 'Args' section provides the only explanations: lead_id is the contact/lead ID and pipeline_id is the pipeline ID. This adds basic clarity but does not go beyond what the parameter names imply, such as format or required relationship.

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 undoes a recent won/lost transition for a lead, using a specific verb and resource. This distinguishes it from siblings like exit_lead_successful and exit_lead_unsuccessful, which create such transitions. However, it does not elaborate on what 'undo' entails (e.g., reverting to previous stage).

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 no explicit guidance on when to use this tool versus alternatives like exit_lead_successful/unsuccessful or move_lead_to_stage. It does not mention prerequisites (e.g., a transition must have occurred) or exclusions. The usage context is only implied by the verb 'undo'.

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