avanan_delete_msp_partner

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 does well by explicitly warning that all tenants associated with the MSP are also deleted, a critical and non-obvious consequence. It does not mention reversibility or downstream effects on users/licenses, but the cascade warning is the most important safety-relevant behavior.

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 two short sentences with no filler. It front-loads the primary action and then adds the critical warning in a dedicated second sentence, so every word earns its place.

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 one-parameter destructive tool with no output schema, the description covers the target, the action, and the most important side effect. It could additionally state the expected response or explicitly confirm irreversibility, but the cascade warning provides the key missing context an agent needs to invoke this safely.

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 coverage is 100%, and the schema already describes msp_id as 'ID of the MSP partner to delete.' The description only restates 'by ID' and adds no new parameter-level meaning. The baseline of 3 applies because the schema carries the parameter documentation burden.

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 the specific verb 'Delete' and names the exact resource ('child MSP partner by ID'), making the operation unambiguous. It also distinguishes this tool from sibling delete tools like avanan_delete_tenant and avanan_delete_msp_user by clearly targeting the MSP partner 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 explicit when-to-use or when-not-to-use guidance is provided beyond the core action. The wording implies this tool is for removing a child MSP partner, but it does not mention alternatives, prerequisites, or situations where the cascade makes deletion inappropriate. This leaves some routing to agent inference.

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