awtrix_delete_app

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

Annotations already declare idempotentHint and destructiveHint, so the core behavioral safety profile is covered. The description adds context beyond the annotations by specifying exactly what is destroyed or affected: a custom app's presence in the display cycle. No contradiction exists between the description and annotations.

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 a single front-loaded sentence with no filler. It states the action, target, scope, and parameter mechanism efficiently.

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?

The tool is simple: one required parameter, an output schema is present, and annotations cover idempotency and destructive behavior. The description covers the essential target and parameter. Minor gaps remain around exact-name matching and the precise meaning of 'from the display cycle', but nothing critical is missing for basic 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?

Schema description coverage is 0%, and the description only indicates that removal happens 'by name'. This adds meaning beyond the raw schema by relating the 'name' parameter to the custom app identifier, but it does not clarify expected format, uniqueness, or matching behavior. For a single simple parameter, this is adequate but minimal.

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 ('Remove'), identifies the exact resource ('a custom app from the display cycle'), and specifies the selection mechanism ('by name'). This clearly distinguishes it from sibling tools like awtrix_upsert_app, which creates or updates an app rather than deleting it.

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 is given about when to use this tool versus alternatives, nor are exclusions or prerequisites mentioned. The intended use is only implied by the tool's name and purpose, not stated.

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