radarr_delete_delayprofile

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

Annotations already set destructiveHint=true, and the description repeats this with 'DESTRUCTIVE: this deletes data.' While this adds emphasis, it does not disclose additional behavioral traits such as permanence, cascading effects, or required permissions. Given annotations cover the destructive nature, the description adds minimal extra value.

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 description is extremely concise: two short sentences. It front-loads the core purpose and adds a warning. There is no fluff or irrelevant detail, making it easy to parse quickly.

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?

The tool is simple with one parameter and an output schema. The description tells the agent it deletes and warns that it is destructive. However, it lacks details about what happens to associated data, whether deletion is reversible, or what the expected outcome might be. While annotations cover safety, the description is minimally adequate.

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?

The schema has one parameter 'id' with no description (0% schema description coverage). The description provides no explanation of what 'id' refers to, such as the delay profile ID, or any format expectations. It fails to compensate for the lack of schema documentation.

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 clearly states 'Delete delay profiles' with a specific verb and resource, distinguishing it from sibling tools like create, list, update, and get delay profiles. It is direct and 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, conditions for deletion, or contrast with other delay profile operations. The description simply states the action without contextual usage hints.

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