cleanuparr_get_dead_torrent_config

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

The annotation readOnlyHint=true already declares the operation as safe/read-only, and the description is consistent with it. However, the description adds no additional behavioral context such as permissions, rate limits, or side effects beyond what the annotation provides.

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, well-formed sentence that is front-loaded with the action and resource. Every word earns its place, with no unnecessary information.

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 single-parameter read operation with an output schema present and annotations covering safety, the description is sufficient. It could be enriched with context about prerequisites or the expected output shape, but the output schema likely fills that gap.

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 input schema has no description for the 'download_client_id' parameter (0% coverage). The description compensates by identifying it as a 'download-client GUID', which clarifies its meaning and purpose in the context of the tool.

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 the verb 'Get', the resource 'dead-torrent settings', and the scope 'for a download-client GUID'. This precisely distinguishes it from sibling tools like 'update_dead_torrent_config' and other config getters.

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?

The description implies usage when you need dead-torrent settings for a specific download client, but it does not explicitly state when to use it over alternatives or any exclusions. No sibling tools are mentioned.

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