Detach a contact

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

No annotations are provided, and the description does not disclose behavioral traits such as what happens when detaching (e.g., effect on related data, permissions needed, idempotency). The brief description fails to inform the agent of important side effects.

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 very short (one line plus tags), but it is not effectively concise—it omits essential information. It includes technical details (HTTP method, tags) that may be redundant for an agent focused on high-level usage.

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 no annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It does not explain the purpose beyond the name, the return value, or any context needed to use the tool safely and effectively.

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 schema coverage is 0%, meaning the description adds no explanation of the parameters. The schema includes 'body.contactId' and 'path.dealId', but the description does not explain how to use them, leaving the agent with no guidance beyond the schema types.

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 ('Detach a contact') and the resource ('from a deal'), with HTTP method and path. However, it does not differentiate from sibling tools like 'weeek_detach_an_assignee' or 'weeek_detach_an_organization', which share similar structure.

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, no prerequisites, no conditions under which detaching is appropriate. The description merely restates the function without usage context.

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