Detach the contact

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

No annotations are provided, so the description must carry the behavioral burden. It only says 'Detach the contact' and gives the HTTP method, which implies a destructive operation. It fails to disclose side effects (e.g., whether the contact is actually deleted or just unlinked), authorization needs, or irreversible changes.

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 short and front-loaded with the HTTP method and path, but it includes extraneous info like 'Tags: Organizations' and 'Body: application/json' that could be omitted. It is concise but fails to deliver necessary detail.

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 output schema, no annotations, and zero schema coverage, the description is severely incomplete. It does not clarify what 'detach' entails, the response format, or any error conditions. A tool with nested parameters and destructive effect demands far more context.

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 0%, and the description does not explain any parameters. The schema indicates required 'organizationId' and 'contactId' but the description adds no meaning to these fields. The agent must infer from parameter names alone.

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 it performs a DELETE request to detach a contact from an organization. The verb-resource pair is direct: 'Detach the contact' along with the HTTP method and path. However, it does not distinguish from sibling tools like weeek_detach_a_contact, leaving ambiguity.

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 on when to use this tool versus alternatives (e.g., when to use detach vs. delete a contact). There is no mention of prerequisites or context like whether the contact must be attached first.

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