trmnl_reset_plugin_setting_credentials

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds useful specifics beyond that: the OAuth credential is removed and the plugin setting is deleted, and the setting is gone afterward so the plugin can be reconfigured from scratch. This is valuable context for a destructive mutation.

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 key destructive effect is front-loaded in the first two sentences. There is some redundancy ('Destructive: the setting is gone afterwards' repeats the prior deletion statement) and a generic closing sentence, but the overall structure is efficient.

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 destructive mutation without an output schema, the description supplies the essential effect, destructiveness, and endpoint. Annotations cover idempotency and open-world behavior, though the description could do more to explain preconditions and when to choose this tool over similar reset/delete/disconnect siblings.

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 does not compensate by explaining the parameters. It merely shows '{id}' in the endpoint path, while the schema already says 'Plugin setting id or uuid'; the profile parameter is not discussed in the description at all.

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 states a specific combined action: forgetting/removing the linked OAuth credential AND deleting the plugin setting. This is clear and more concrete than the tool name alone, but it does not explicitly contrast itself with closely related siblings such as trmnl_delete_plugin_setting or trmnl_disconnect_plugin_settings_connection.

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?

Usage is implied by phrases like 'so the plugin can be set up again from scratch' and the destructive warning. However, it never says when to use this instead of siblings that only delete the setting or only disconnect the OAuth connection, leaving meaningful routing decisions to the agent.

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