trmnl_delete_plugin_setting

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so 'Changes remote state or starts work' merely restates the structured flags and is even imprecise for a delete. Nothing is said about what is destroyed (configuration, credentials, logs), whether the deletion is recoverable, or what happens to dependent data.

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?

Short and front-loaded with the action, but two of the three sentences are boilerplate safety text that carry no tool-specific information.

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 an irreversible destructive mutation with no output schema and a nested path parameter, the description omits the essentials: irreversibility, scope of deletion, and the existence of a related removal-preview tool.

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 coverage is only 50% and the description adds nothing about the nested `path.id` or the `profile` parameter. With the nested object and a profile selector, the description should compensate for the documented gap but does not.

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 and resource ('Delete a plugin setting') and pins it to the endpoint DELETE /api/plugin_settings/{id}, so the agent knows exactly which resource is affected. It does not, however, distinguish itself from near-siblings such as trmnl_remove_plugin_setting_transform or trmnl_clear_plugin_setting_state.

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?

Only guidance is the generic 'Run only within the user-authorized scope', which applies to every mutating tool and offers no selection criteria. There is no mention of when deletion is appropriate versus the removal-preview or transform-removal siblings.

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