Detach numbers from campaign

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

Annotations already indicate destructiveHint=true. The description adds valuable behavioral details: the effect on SMS capability, response format (per-TN lists with specific failure reasons), non-standard envelope, and error codes (INVALID_PAYLOAD, NOT_FOUND, TNIQ_ERROR). No contradiction.

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 sentences, front-loaded with action and resource, each sentence adds critical information. 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 2-parameter tool with no output schema but good annotations, the description covers purpose, effect, response structure, and errors. An agent can correctly invoke and interpret the tool response.

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 100%, so baseline is 3. The description does not add any parameter-specific meaning beyond what is already in the schema descriptions (id and phone_numbers are well-described in 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 uses specific verb 'Detach' and clearly states the resource 'telephone numbers from one of your 10DLC campaigns'. It distinguishes from sibling tools like msg_assign_numbers (assign) and msg_list_numbers (list) by focusing on removal.

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?

Description implies usage context (when removing numbers from a campaign) and notes the consequence (numbers can't send SMS until re-attached). It doesn't explicitly state when not to use or list alternatives, but the context is sufficient for differentiation.

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