cleanuparr_delete_download_client

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

The annotations include destructiveHint: true, but the description adds no extra behavioral context beyond the fact that it deletes. It does not mention whether the deletion is permanent, affects related data, or requires confirmation. Since the annotation already covers destructiveness, the description contributes little beyond that.

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 a single concise sentence that is front-loaded with the action and resource. Every word earns its place, with no unnecessary detail.

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 description is adequate for a simple delete operation with one parameter and an existing output schema. However, it lacks contextual guidance about when to use this tool or what happens after deletion, and it doesn't reference sibling tools or any side effects.

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 provides client_id as a string with no description (0% coverage). The description compensates by specifying that the client is identified by GUID, which adds semantic meaning to the parameter. However, it does not explain how to obtain the GUID.

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 'Delete a download client by GUID.' clearly states a specific action (delete) on a specific resource (download client) with a specific identifier (GUID). This distinguishes it from sibling tools like create, update, or test download clients.

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 vs alternatives, such as when to use update_download_client instead or any prerequisites. The usage is only implied by the verb 'Delete'.

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