btp_delete_subaccount

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

With no annotations provided, the description carries the full burden. It warns that the action is permanent and deletes all resources, which is a critical behavioral trait. However, it lacks detail on idempotency, authorization requirements, or whether confirmation is needed. The warning adds value but is not comprehensive.

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 very concise with only two sentences and no fluff. The warning is appropriately front-loaded. However, it could briefly mention parameter usage without becoming verbose, which would improve informativeness while maintaining 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 simplicity of the tool (delete operation) and the lack of output schema, the description should at least explain how to identify which subaccount to delete via parameters. It does not, making it incomplete for agent use. The warning alone is insufficient for correct invocation.

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 parameters 'args' and 'kwargs' are completely undocumented in the description. With 0% schema coverage, the description must explain how to specify the subaccount, but it fails to do so. The agent has no clue what to input.

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 'Delete a subaccount permanently' with a specific verb and resource. It distinguishes the tool from its siblings that are for listing, getting, or creating subaccounts, making it unequivocally the delete operation.

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 guidance on when to use this tool versus alternatives. The warning implies it should be used with caution and only when permanent deletion is intended, but does not provide context such as prerequisites or when not to use it.

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