remove_lead_from_audiences

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'Remove' which implies mutation, but does not explain side effects (e.g., does the lead remain in other audiences?), error handling (e.g., lead not found), or required permissions. This is insufficient.

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 long, with the first sentence stating the core purpose and the second adding a key requirement. No unnecessary words, and the key information is front-loaded. Every sentence earns its place.

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 the simplicity of the tool (single action, no nested objects, no output schema), the description covers the main purpose and the identifier requirement. It could mention the result of the operation (e.g., success/failure) or idempotency, but for a removal action it is mostly complete.

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%, so the baseline is 3. The description adds value by stating that the lead must be identified by at least one identifier, clarifying the relationship among the multiple identifier parameters (crm_id, twitter, etc.). This goes beyond the individual parameter descriptions.

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: 'Remove a lead from one or more audiences.' It specifies the resource (lead) and the target (audiences), and adds the requirement to identify the lead by at least one identifier. This distinguishes it from sibling tools like create_or_update_lead or search_lead.

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 a prerequisite ('Identify the lead by at least one identifier') but does not explicitly state when to use this tool versus alternatives, nor does it discuss exclusions or when not to use it. The context is clear enough for a simple removal action, but lacks deeper guidance.

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