application_delete

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

Annotations already mark the tool as destructive, and the description adds important context by stating that all of the application's devices are also deleted. This goes beyond the annotation by specifying what exactly is affected, which is valuable for an agent to warn users or confirm scope.

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?

A single sentence with no filler, front-loaded with the action and resource, and including the crucial cascade detail. 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 simple delete operation with one parameter, the description covers the key information: what is deleted and the cascade. An output schema exists so return values need not be described, and the destructive annotation covers permanence. Nothing critical is missing.

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?

With 0% schema description coverage, the description does not compensate by explaining the 'application_id' parameter. However, the parameter name is self-explanatory and the description implies the need to identify an application. The single parameter is simple enough that the lack of explicit documentation is a minor gap.

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 a specific verb ('Delete') and resource ('application'), and further specifies the cascading effect on associated devices. This clearly distinguishes it from other application tools like application_get or application_update.

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 when an application and its devices need to be removed, but does not explicitly discuss when to choose this tool over alternatives or mention any exclusions. The intent is inferred from the verb and resource rather than spelled out.

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