trmnl_remove_plugin_setting_transform

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

Annotations already flag destructiveHint and idempotent, but the description adds genuine context beyond them: which file is deleted, that the associated language is forgotten, and that rendering falls back to raw fetched data. It does not state whether the change is recoverable or what permissions are needed, keeping it short of a 5.

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 core statement is front-loaded and tight, but the raw endpoint line 'TRMNL DELETE /api/plugin_settings/{id}/transform.' is redundant metadata, and the generic trailing sentence 'Changes remote state or starts work' repeats what the annotations already say.

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, parameterized mutation with annotations covering the safety profile and no output schema required, the description covers the effect and post-condition well enough to call it correctly. The remaining gaps are permission/reversibility details and any mention of the parameters.

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?

With only 50% schema description coverage and a nested path object, the description supplies no parameter meaning at all – it never mentions that path.id identifies the plugin setting or what profile selects. An agent must rely entirely on the schema strings.

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 first line states a precise verb and resource ('Remove the transform script of a private plugin'), and the follow-up clarifies the concrete effect (deletes the serverless transform file). It is clearly distinguishable from sibling removal tools such as trmnl_remove_plugin_setting_featured_image, though it never explicitly contrasts itself with a modify/replace-transform path.

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 only implied: you call this when a plugin should no longer transform fetched data. Beyond the generic guardrail 'Run only within the user-authorized scope', there is no guidance on when to remove versus update/replace the transform (e.g. trmnl_update_plugin_setting) or what preconditions exist.

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