Check tuner count vs jellyfin

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing on top of that: no mention that it contacts an external Jellyfin server, what auth/credentials are required, whether the comparison can fail, or what kind of discrepancy it reports.

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?

It is a single short sentence with no padding, but that brevity reflects under-specification rather than conciseness of content. Nothing is front-loaded because there is nothing substantive to front-load.

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?

An output schema exists, so return values needn't be explained, but the tool requires two credentials and an external service call — none of that operational context is present. For a cross-system check with 4 undocumented params, this description leaves the agent without enough to call it confidently.

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?

Four parameters with 0% schema description coverage, and the description provides zero parameter semantics. The required jellyfin_url and jellyfin_api_key, plus device_id and info, are completely undocumented — the agent cannot know which device is compared, what 'info' should contain, or what form the API key takes.

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 is a tautology: 'Invoke the check_tuner_count_vs_jellyfin operation' only restates the tool name and title. It adds no verb+resource specification beyond what the identifier already implies, and gives no clue what a 'tuner count vs Jellyfin' comparison actually produces or why an agent would want it.

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 when-to-use guidance, no exclusions, and no reference to any alternative among the large set of sibling hdhomerun_check_* tools (e.g. hdhomerun_check_device_reachable, hdhomerun_check_firmware_model). The agent must infer entirely on its own when this check is the right call.

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