remove_contact_from_automation

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

No annotations present, and the description only mentions the removal action. It does not disclose idempotency, error cases, permission requirements, or whether the operation is reversible. Minimal behavioral insight.

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 succinct sentences: first states purpose, second provides actionable guidance. No redundancy or unnecessary words.

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 tool with one parameter and an output schema, the description covers purpose and parameter source. However, missing behavioral details (e.g., what happens if contact not in automation) and lack of output schema explanation leave gaps in completeness.

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?

With 0% schema description coverage, the description adds value by explaining the source of the required parameter (list_contact_automations) and its purpose. This compensates for the lack of schema documentation.

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?

Description clearly states the action ('Remove a contact from an automation') with specific verb and resource. It distinguishes from sibling 'add_contact_to_automation' implicitly, but does not explicitly contrast with other similar tools.

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?

Provides a prerequisite by telling the user to get contact_automation_id from list_contact_automations. However, it does not elaborate on when to use this tool versus alternatives like remove_tag_from_contact or unsubscribe_contact_from_list.

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