cleanuparr_test_download_client

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

The annotation destructiveHint=true already indicates potential side effects, but the description adds no extra behavioral context. It does not explain what 'test' entails, whether connections are attempted, or if changes occur. No contradiction exists, but the description fails to elaborate beyond the annotation.

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?

A single concise sentence contains the core purpose and a brief structural hint. No unnecessary words or redundant 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 tool with a nested object parameter and a destructive hint, the description is thin. It does not explain how to construct the client object beyond a partial field list, nor what a successful test implies. The output schema exists but the description doesn't cover side effects or error states.

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 defines only a generic 'client' object with additionalProperties:true and 0% description coverage. The description lists fields (typeName, type, host, credentials, urlBase, optional clientId) that provide some structure. However, it is ambiguous whether this refers to the input parameter or the output DTO, and it lacks type and requirement details beyond 'optional clientId.'

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: 'Test a download client.' This clearly conveys the tool's action. It doesn't explicitly distinguish from the similar 'Test an ARR instance' sibling, but the resource name 'download client' provides inherent differentiation.

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 regarding when to use this tool versus alternatives such as cleanuparr_test_arr_instance. There is no mention of prerequisites, context, or situations where this tool is or isn't appropriate.

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