radarr_get_system_status

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

No annotations are provided, so the description carries the full behavioral burden. It correctly implies a read-only operation and lists returned fields, but does not disclose whether authentication is required, whether it is cached, or any rate limits. For a zero-parameter diagnostic tool, more context about safety and side effects would be expected.

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?

Two short sentences, front-loaded with the purpose and then the returned information. Every word earns its place with no redundancy.

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 (no parameters, no output schema), so the description covers the core purpose and output fields. However, without annotations or output schema, it leaves behavioral gaps such as authentication requirements, and it does not differentiate from the sibling radarr_get_health, which may confuse an agent choosing between diagnostic endpoints.

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?

With zero parameters, the baseline is 4. The description appropriately focuses on output rather than inputs, and no parameter semantics are needed.

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?

States a specific verb (Get) and resource (system status), and enumerates the concrete fields returned (version, OS, .NET version, database type, migration version). It is clearly distinguished from siblings like radarr_get_health or radarr_get_quality_profiles, though the description could explicitly contrast with get_health since both are diagnostic endpoints.

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?

There is no guidance on when to use this tool versus alternatives such as radarr_get_health or radarr_get_queue. The description only says what it returns, not the context or conditions that would prompt an agent to call it.

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