pause_lead

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a state change ('pause') but doesn't clarify if this is reversible, what permissions are required, how it affects campaign metrics, or what happens to scheduled communications. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'pause' entails operationally, what the expected outcome is, or how it differs from similar tools. Given the complexity of lead management and rich sibling toolset, more context is needed.

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%, with both parameters clearly documented in the schema. The description adds no additional parameter context beyond implying that 'campaign_id' and 'lead_id' identify the target, which the schema already covers. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('pause') and target resource ('a lead in a campaign'), making the purpose immediately understandable. It distinguishes from siblings like 'resume_lead' by specifying the opposite action, though it doesn't explicitly contrast with other lead management tools like 'delete_lead_from_campaign' or 'unsubscribe_lead_from_campaign'.

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?

No guidance is provided on when to use this tool versus alternatives like 'resume_lead', 'delete_lead_from_campaign', or 'unsubscribe_lead_from_campaign'. The description lacks context about prerequisites (e.g., lead must be active) or typical scenarios for pausing versus other actions.

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