Bulk unsubscribe

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

Annotations already declare non-readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious traits: it returns a job id for polling via plunk_get_bulk_job_status, and it prompts for confirmation before running. It stops short of stating whether an unsubscribe is reversible or how partial failures are handled.

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?

Labeled sections (Purpose / Not for / Returns / Use when / Note) with the key routing information front-loaded. No sentence is redundant and each block 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?

With no output schema, the description correctly covers the return contract (job id + the polling tool) and the confirmation behavior, and annotations cover the mutation profile. An agent has everything needed to call this correctly.

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?

The single parameter has 0% schema description coverage, so the description must carry the load. It restates the 1000-item cap that already lives in the schema's maxItems, but adds nothing about the required contactIds format (UUIDs), ordering, or behavior for unknown/nonexistent ids. Partial compensation only.

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 ('opt up to 1000 contacts out of marketing email') with the scale bound included, and explicitly names the operation it is not ('Deleting them, which is plunk_bulk_delete_contacts'). An agent can distinguish this from plunk_bulk_delete_contacts and plunk_unsubscribe_contact without opening any 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?

Gives an explicit exclusion ('Not for: deleting') with the alternative tool named, plus concrete when-to-use scenarios ('honouring a batch of opt-out requests, or suppressing a cohort'). Nothing about tool selection is left to inference.

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