unsubscribe_contact_from_list

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

The description lacks any behavioral details beyond the name. It does not disclose idempotency, error conditions, side effects, or authorization requirements. Since no annotations are provided, the description carries full burden but only states the basic operation.

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 too minimal: a single sentence that adds no detail beyond the tool's name. While it is front-loaded, it fails to provide necessary context, making it under-specified rather than concisely informative.

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?

Given the tool's complexity (2 parameters, no annotations, no output schema details, and multiple sibling tools), the description is completely inadequate. It omits parameter descriptions, behavioral traits, and usage context, leaving the agent unable to use the tool 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?

With 0% schema description coverage, the description must compensate by explaining the parameters, but it does not. The two required parameters ('contact_id' and 'list_id') are not described, leaving the agent without guidance on their format, source, or meaning.

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 clearly states the action and resource: 'Unsubscribe a contact from a list.' It uses a specific verb and identifies the resource, distinguishing it from related tools like 'subscribe_contact_to_list'. However, it does not explicitly differentiate from siblings such as 'remove_tag_from_contact' or 'add_tag_to_contact', which have different purposes.

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. The description does not mention prerequisites, when not to use it, or comparison with siblings like 'subscribe_contact_to_list' or 'remove_contact_from_automation'.

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