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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds the irreversibility guarantee ('Cannot be undone') and a user-confirmation obligation, which go beyond the annotation vocabulary. It does not mention permissions/auth or what happens to already-sent messages.

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?

Two short sentences, zero filler, with the irreversible-delete warning and the identifier source front-loaded. Every clause 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?

For a simple, single-resource delete with full annotations and no output schema, this covers identity, sourcing, irreversibility and a confirmation rule. Only permission requirements and behavior for in-flight enrolled contacts are left unstated, a minor gap.

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 nominally 100%, but the welcomeId schema text reads 'Delete and enrollExisting.', which is garbled and unhelpful. The description compensates by telling the agent exactly where to obtain welcomeId, adding genuine meaning the schema fails to provide.

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 (Delete) plus resource (welcome message) and explicitly sources the required identifier from a named sibling tool (list_welcome_messages). An agent can separate this from create_welcome_message, update_welcome_message and set_welcome_message_active 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 a concrete precondition ('welcomeId from list_welcome_messages') and an interaction rule ('confirm with the user first'), which is more than most delete tools offer. It does not name an alternative path (e.g. set_welcome_message_active to disable instead of deleting), so it stops short of full when/when-not routing.

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