Detach an organization

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

With no annotations, the description must disclose behavior. It only shows the HTTP method and endpoint, but does not mention side effects (e.g., whether the organization is permanently removed or can be reattached), required permissions, or any destructive actions beyond the DELETE method.

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 concise (one sentence plus endpoint), but this brevity sacrifices crucial information. It lacks structure and does not earn its place by providing sufficient guidance.

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 absence of annotations and output schema, and the complexity of two nested object parameters, the description is severely incomplete. It fails to explain the tool's operation, parameter semantics, or usage context, making it minimally helpful.

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%, yet the description adds no meaning to the parameters. It only mentions 'Body: application/json' but does not explain the required fields 'organizationId' or 'dealId', leaving the agent to rely solely on the schema.

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 states 'Detach an organization' and includes the endpoint 'DELETE /crm/deals/{dealId}/organizations', clearly indicating it removes an organization from a deal. The verb 'detach' and resource 'organization' are specific, but the context of being from a deal is implied by the endpoint rather than explicitly stated.

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 sibling tools like 'weeek_detach_a_contact' or 'weeek_detach_an_assignee'. There is no mention of alternatives, prerequisites, or conditions for use.

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