contacts_delete_contact_from_workflow

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

Annotations indicate destructiveHint=true and idempotentHint=true, so the agent knows it is destructive and idempotent. However, the description adds no behavioral context beyond this—it does not mention that the action is permanent, what happens to the contact's progress, or any additional effects. Since annotations already provide the safety profile, a score of 2 reflects that the description contributes nothing extra.

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 a single phrase, which is overly terse rather than concisely informative. It lacks even a full sentence to provide context. While brevity is generally good, here it results in under-specification, making the description unhelpful for an agent understanding the tool's purpose and behavior.

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 operation, this description is incomplete. It does not inform the agent about the effect on the contact, whether the contact is removed from the entire workflow or just a specific step, or any follow-up actions. The absence of an output schema and minimal description leaves significant gaps for an agent 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?

Schema description coverage is 67% (contactId and workflowId have descriptions; eventStartTime does not). The description adds no information about any parameter, especially the optional eventStartTime, which is entirely unexplained. It relies solely on the sparse schema descriptions, and the missing third parameter remains a mystery without additional context.

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 'Delete Contact from Workflow' is essentially a restatement of the tool name. It conveys the action (delete) and the object (contact/workflow) but adds no specifics about what this operation entails, such as whether it removes the contact from all workflow steps or has any side effects. It does not differentiate from similar delete operations like contacts_remove_contact_from_campaign.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like contacts_add_contact_to_workflow, contacts_remove_contact_from_campaign, and contacts_remove_contact_from_every_campaign, the description gives no hint about the appropriate context, prerequisites, or how it differs from those.

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