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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered upstream. The description's only added behavioral signal is blast radius ('all sequences'), which is genuinely useful; it says nothing about reversibility, whether the lead is also blocklisted, or per-workspace effects.

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?

Very short and front-loaded, with the scope qualifier arriving immediately. The opening 'Unsubscribe Lead Globally -' redundantly restates the title, which is the only wasted text.

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?

Output schema exists and annotations carry the destructive/safety profile, so the definition is broadly sufficient. The remaining gap is that a destructive, global-scope action should hint at irreversibility or recovery paths, which is absent.

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% with both id and workspace_id fully documented, and the schema explains the workspace fallback behavior. The description contributes nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource with an important scope qualifier: 'Unsubscribe a lead from all sequences'. The 'all sequences' phrasing implicitly distinguishes it from the sibling unsubscribe_lead_from_sequence, though it never names that sibling.

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?

Usage is only implied by the word 'Globally' and 'all sequences'; an agent can infer this is the broad-scope variant, but the description never states when to prefer it over unsubscribe_lead_from_sequence or whether prerequisites/confirmations apply.

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