distributions_delete

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

With no annotations, the description carries the burden. It discloses required licenses and the consequence that new agents (including VDI) cannot register after deletion. However, it does not explicitly state whether deletion is permanent/irreversible or what happens to existing agents, leaving some behavioral ambiguity.

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 well-structured and each section earns its place: purpose, parameter sourcing, behavioral note, license, and example. It is slightly verbose with blank lines but remains efficient.

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 destructive action with one parameter, the description provides enough context: usage, effect, license, example, and endpoint. It does not cover error conditions or output, but with no output schema and a simple action, the missing pieces are acceptable.

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?

Given the context signal of 0% schema description coverage, the description fully compensates. It explains that distribution_id is required, where to find it (Create distributions API response or Agent Installations screen), and provides an explicit example request body, adding meaning beyond the schema's minimal 'Installation package distribution ID.'

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 starts with 'Delete agent installation packages' – a specific verb and resource. It clearly distinguishes from sibling distribution tools (create, get_versions, get_status, etc.) by indicating this is the deletion 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?

Clear context: it's used to delete a distribution, with a note about the effect on new agents. However, it does not explicitly mention when not to use it or alternative tools (e.g., distributions_create to make a new package), stopping short of the 'explicit when/when-not/alternatives' bar.

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