delete_app

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

With no annotations, the description carries the burden of disclosing behavior. It transparently reveals a key nuance: the source repository is kept unless 'delete_repository' is true. This is valuable behavioral context beyond the schema. It does not mention irreversibility or side effects, but the key conditional behavior is clear.

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, front-loaded with the core action and immediately followed by the clarifying detail. Every word earns its place, with no fluff.

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 simple delete operation, the description covers the primary action and the important conditional behavior. It does not detail return values or side effects, but an output schema is present and the operation is straightforward. It is sufficient for safe 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 description directly explains the 'delete_repository' parameter, which is the non-obvious one, by stating that the repository is kept unless it is true. The 'name' parameter is not explicitly described, but it is self-evident from the tool name and context. With 0% schema coverage, this description compensates well for the critical parameter.

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 the tool's purpose: 'Delete an app.' It uses a specific verb and resource, and the added nuance about the repository distinguishes it from sibling tools like unpublish_app or update_app.

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 description implies usage for deleting apps, and the repository caveat gives some conditional guidance. However, it does not explicitly state when to choose this over alternatives (e.g., unpublish_app for temporary removal) or mention any prerequisites or exclusions.

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