avanan_delete_tenant

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

The description includes a prominent warning about deleting the tenant and all its data, which is critical for a destructive operation. However, it does not mention reversibility, prerequisites, or any required permissions.

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 with two sentences: one stating the purpose and one delivering a clear warning. Every word is necessary and front-loaded.

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 simple delete operation with one parameter and no output schema, the description covers the essential behavioral warning. However, it could mention what happens after deletion (e.g., response, cleanup) or any dependencies.

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 fully describes the single parameter 'tenant_id' with a concise description. The tool description adds no additional meaning beyond the schema, yielding a baseline score.

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 specific resource ('a customer tenant by ID'), and the warning distinguishes it from related tools like 'avanan_get_tenant' or 'avanan_create_tenant'.

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?

The description implies that this tool should be used carefully due to data destruction, but does not explicitly state when to use it over alternatives or provide conditions to avoid misuse.

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