lidarr_get_health

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

No annotations provided. The description states 'shows any problems detected', implying a read-only informational operation but does not explicitly declare it non-destructive or detail side effects. With no annotations, the description carries burden but is minimal.

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?

Single sentence, front-loaded with verb, 14 words, no fluff. Every word earns its place.

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 zero-parameter tool with no output schema, the description explains purpose and source. However, it lacks examples of issues or return format, which could enhance completeness. Still adequate.

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?

No parameters exist, and schema coverage is 100%. The description adds no additional parameter meaning beyond the empty schema. Baseline is 3 per high coverage rule.

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' and resource 'health check warnings and issues', specifying it's from Lidarr (Music). This distinguishes it from sibling health tools for Radarr/Sonarr. No tautology.

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 checking problems but offers no explicit guidance on when to use versus alternatives (e.g., other lidarr tools or other health tools). Usage is inferred from purpose.

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