drouting_delete_carrier

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

Description only states 'delete' without explaining consequences, such as whether the deletion is reversible, if it triggers a reload (though a reload parameter exists), or if it requires specific permissions. With no annotations, this is insufficient.

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 extremely concise at one sentence, but it effectively communicates the core purpose. No unnecessary words, though it could be expanded slightly 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 presence of an output schema and two parameters (one with a default that suggests behavioral impact), the description lacks critical context such as what happens after deletion, whether the reload parameter is necessary, and any dependencies or prerequisites.

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 purpose of the 'id' or 'reload' parameters. The schema itself provides basic info (type, default), but the description adds no value beyond that.

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 the action (delete) and the resource (dynamic routing carrier by id). It distinguishes from siblings like drouting_add_carrier or drouting_list_carriers, but does not elaborate on what a dynamic routing carrier is or the context of deletion.

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 provided on when to use this tool versus alternatives (e.g., drouting_update_carrier to modify instead of delete). No mention of prerequisites or side effects.

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