avanan_delete_msp_user

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Delete', which states the action but does not disclose whether deletion is permanent, whether it cascades to related resources, or what response/error behavior to expect. For a destructive operation this is a meaningful gap.

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 with no wasted words. It front-loads the operation and the identifying parameter, making it easy to scan.

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?

The tool is a simple one-parameter delete operation, so the description covers the basic 'what' and 'how' adequately. However, because there is no output schema and no annotations, the absence of any behavioral or safety context leaves the agent under-informed about irreversible side effects or post-deletion expectations.

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 the schema already documents user_id as 'MSP user ID.' The description adds minimal semantic value by restating that deletion is 'by ID', but this is consistent with the parameter and not misleading.

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 a specific verb ('Delete'), a specific resource ('MSP user'), and the selection criterion ('by ID'). It is immediately distinguishable from sibling tools like avanan_delete_msp_partner or avanan_update_msp_user.

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 intended use is clearly implied by the delete verb, but there is no explicit guidance about when to choose this over alternatives or any caution about destructive consequences. It reads as a straightforward action statement rather than usage guidance.

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