Delete a setting

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds the required permission scope, which is real value beyond structured data. However, it does not say that the deletion is permanent/irreversible, nor that execution is gated by confirm="YES" and dry_run defaulting to true — meaningful behavior for a destructive tool even though the schema documents those fields.

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?

Three short sentences, but the second ('Deletes an existing setting specified by its ID') largely restates the first. Front-loading is fine; the redundancy costs it the top band.

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?

Annotations, a full-coverage schema and an output schema carry most of the burden, and the permission note fills an important gap. Still, for an irreversible destructive operation the description omits the confirmation/dry-run workflow and the permanence of the effect, leaving a real gap for an agent deciding how to call it.

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 100%, so setting_id, confirm and dry_run are already well documented in the schema. The description only echoes that the setting is identified by its ID and adds no format examples or semantics beyond that, so baseline 3 applies.

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?

States a specific verb+resource ('Delete a setting') and clarifies the selector ('specified by its ID'), which is enough to separate it from the many delete_* siblings by resource type. It doesn't explicitly contrast with update_setting or list_settings, but the resource+verb pairing is unambiguous.

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 only guidance is the permission requirement ('Perm: manage_advanced_settings'), which is useful as a gate but does not say when to prefer deletion over updating a setting, or what prerequisites/state the setting must be in. Usage is implied by the tool name rather than explained.

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