trmnl_delete_user_theme

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the mutation profile is known. The description adds the theme-builder prerequisite and authorization scope, but much of its wording ("Changes remote state or starts work") is generic and it does not explain deletion permanence or side effects.

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 definition is short and front-loads the core action followed by the prerequisite and endpoint. The generic remote-state and authorization sentence is slightly boilerplate but not harmful.

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 destructive tool, the description plus annotations and schema provide enough to call it: action, required id, prerequisite, and safety scope are covered. It could be stronger if it explicitly stated irreversibility or any cascade behavior.

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 50%, with the id and profile parameters described in the schema. The description adds endpoint context ("DELETE /api/user_themes/{id}"), reinforcing that the required id identifies a user theme, but it says nothing about the profile parameter.

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 verb and resource: "Delete a theme." It is clearly a deletion tool for user themes, though it does not explicitly contrast itself with sibling update/get/create theme tools.

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?

It provides a prerequisite (theme builder must be enabled) and a safety boundary (run only within user-authorized scope). However, it does not say when to choose deletion versus updating or importing a theme, nor does it describe preconditions beyond the builder flag.

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