Advance a lead

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

No annotations provided, so the description carries full burden. It discloses key behaviors: moving through stages, refreshing next action, and terminal states (Won/Lost). However, it does not address the effects on notes or nextActionDate, or whether changes are reversible. Adequate but not comprehensive.

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?

Two sentences, front-loaded with the primary action. No extraneous words. Every sentence serves a purpose: stating the core function and highlighting terminal behavior.

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?

Given 5 parameters, no output schema, and no annotations, the description covers the main workflow (stage progression, next action) but omits notes and nextActionDate context. It is adequate for basic use but leaves gaps for a new agent unfamiliar with CRM concepts.

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 0%, so the description must add meaning. It explains stage (funnel movement, close-out) and nextAction (refresh). But it does not explain notes or nextActionDate, leaving some parameters underspecified. The description adds some value beyond schema names but is incomplete.

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 purpose: 'Move a lead through the funnel and refresh its next action. Won/Lost closes it out.' It uses a specific verb ('move,' 'advance') and resource ('lead'), and distinguishes from sibling tools like lead_capture (creating leads) and pipeline_view (viewing).

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 when to use (to advance a lead stage, refresh next action, or close via Won/Lost). While it does not explicitly exclude scenarios or name alternatives, the context is clear given sibling tool names (e.g., lead_capture for new leads).

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