Delete Call

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

Annotations already indicate destructiveHint: true, so the description merely reinforces the destructive nature with 'Permanently delete.' No additional behavioral details (e.g., irreversibility, required permissions) are disclosed. The description does not contradict the annotations.

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 a single, clear sentence that is concise and front-loaded. However, it could include a brief warning about destructiveness without losing conciseness.

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 destructive nature, the description lacks completeness by not mentioning that the action cannot be undone or any potential side effects. There is no output schema, so the return behavior is entirely unspecified. Minimal information beyond the basics.

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 input schema provides a description for the single parameter callId: 'Call ID to delete (required).' The description adds no further meaning, staying within the schema coverage. With 100% schema coverage, the description's contribution is neutral.

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 'Permanently delete a call record from Hyros,' specifying the exact verb (delete), resource (call record), and the permanent nature. It effectively distinguishes from sibling tools like create_call or get_calls.

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. The description lacks information about prerequisites, context, or when not to use it. The sibling list is extensive but no differentiation is given.

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