Bulk delete contacts

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

Beyond annotations (which already signal destructiveHint/idempotentHint), the description adds the cascade effect on event histories, the loss of the opt-out record, an interactive confirmation step, and a return value (job id to poll) pointing to plunk_get_bulk_job_status. This is exactly the extra context structured fields cannot carry.

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?

Bold-labeled sections put purpose first and then route usage, return, and confirmation; every sentence carries distinct information with no repetition of the name or title.

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 destructive bulk mutation with no output schema, the definition covers purpose, the alternative, the async follow-up tool, and the confirmation gate, and the annotations cover the safety profile. Nothing needed to call it correctly is missing.

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?

Coverage is 0% and there is one parameter, contactIds, whose meaning is only inferable from its name plus the schema's uuid format/pattern and maxItems. The description echoes the 1000 cap but adds no field-level guidance (e.g., where ids come from, behavior on unknown/duplicate ids), so it neither compensates for the coverage gap nor does poorly.

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 scope ("Permanently delete up to 1000 contacts and their event histories") that mirrors the schema's maxItems constraint, and directly contrasts with the doing-nothing-else alternative. An agent can place it against plunk_bulk_unsubscribe_contacts and plunk_delete_contact without opening a schema.

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?

Contains an explicit "Not for" clause naming the sibling tool (plunk_bulk_unsubscribe_contacts) plus the consequence that selects against it (loses opt-out record), and a "Use when" clause for the positive case. Both when-to-use and when-not-to-use are covered.

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