Delete the phone

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

The description lacks any behavioral disclosure. No annotations are provided, so the description must cover aspects like irreversibility, permission requirements, or side effects. It only states 'Delete the phone', omitting critical information for a delete 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 very short but includes redundant information ('DELETE /crm/organizations/{organizationId}/phones/{phoneId}') that repeats the tool name and schema. It fails to provide useful content in a concise manner, making it under-specified.

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 (delete operation with nested parameters, no output schema, no annotations), the description is severely incomplete. It does not specify what happens after deletion, response format, or any dependencies, leaving the agent without essential 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%. The description does not explain the 'path' parameter or its sub-properties organizationId and phoneId. The input schema is empty of descriptions, and the tool description adds no meaning beyond the schema structure.

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 'Delete the phone', specifying the action and resource. However, it does not differentiate from the sibling tool weeek_delete_the_phone_2, which likely deletes a different phone entity.

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 usage guidelines are provided. There is no indication of when to use this tool versus alternatives like weeek_delete_the_phone_2, nor any prerequisites or context like the need for an existing organization and phone ID.

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