radarr_ping

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds value by specifying that the ping also verifies authentication, which goes beyond a simple network reachability check. It does not describe error responses, but given the output schema exists and the tool is trivial, this is acceptable.

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, direct sentence that immediately conveys the tool's function. It contains no fluff or redundant technical jargon, earning a top score for conciseness.

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?

Given the simplicity of the tool (no parameters, read-only annotation, output schema present), the description is fully sufficient to understand what the tool does and what to expect. There are no hidden behaviors or prerequisites to disclose.

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 tool has zero parameters, and schema coverage is 100%. The description correctly implies no input is needed. Per the baseline rule for 0 params, a score of 4 is appropriate.

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 uses a specific verb 'Ping' with a clear resource ('the server') and states the purpose ('verify it is reachable and authenticated'). It clearly distinguishes this tool from all other radarr_* tools, none of which serve as a basic connectivity check.

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 for verifying server availability and authentication, which is a common preliminary check. Though it doesn't explicitly mention alternatives, no sibling tool serves the same function, so the context is clear enough. It could have added a note like 'Use this to confirm the server is up before other operations' but it's not necessary.

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