Delete Package

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

Beyond the annotations, the description discloses the 422 dependency failure, the need to move users before deletion, and the reseller authentication requirement rather than user impersonation. It also explains the 404 case, adding meaningful operational context for a destructive operation.

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?

Three tight sentences front-load the action, then immediately cover the failure precondition, authentication constraint, and error handling. Every sentence carries distinct operational information with no filler.

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 single-parameter destructive tool with an output schema and rich annotations, the description covers the missing pieces an agent needs: preconditions, auth scope, and error interpretation. Nothing material is left unspecified.

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?

There is only one parameter, 'name', and schema description coverage is 100%, so the schema already documents its format and constraints. The description does not add syntax or naming semantics beyond what the schema provides.

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 opens with a specific verb and resource ('Deletes a package'), making the operation unambiguous. It also clarifies the reseller-level scope, though it does not explicitly contrast with other package-management siblings beyond naming set_reseller_user_package as a prerequisite step.

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?

It states exactly when deletion fails (422 while users are on the package) and tells the agent what to do first via the sibling tool set_reseller_user_package. It also specifies the required authentication context and the meaning of a 404, leaving little to inference.

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