dashbrr_delete_settings

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

Annotations already indicate destructiveHint=true, and the description adds context by stating 'This removes the service from the dashboard', clarifying the exact destructive effect. The prerequisite to list settings first also adds useful behavioral context beyond the annotation, though it does not detail irreversibility or permissions.

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 sentences, front-loaded with the purpose, then adds the parameter detail and prerequisite. Every sentence serves a purpose with no wasted words.

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 one-parameter destructive tool with annotations already declaring destructive behavior, the description provides the necessary action, parameter semantics, and a safety prerequisite. No output schema is present, so return values need not be detailed. The tool is fully understandable and actionable.

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 schema only defines 'instance' as a string with no description, so the description carries the full burden. It explains that 'instance' is the type-prefixed instanceId and gives the example 'sonarr-1', fully compensating for the 0% schema description coverage.

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 service configuration from the dashbrr instance' with a specific verb and resource. It distinguishes from sibling tools like dashbrr_delete_sonarr_queue_item by specifying service configuration, and provides the instance format example.

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?

Provides a clear prerequisite: 'use dashbrr_list_settings first'. This gives explicit when-to-use guidance for discovering valid instance IDs. However, it does not explicitly mention when not to use the tool or alternatives (e.g., using dashbrr_save_settings for modifications), so it falls short of a 5.

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