Get sys debug

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds only the scope word 'device-wide' and says nothing about volume or volatility of the debug output, rate limits, or what the raw dump looks like — minimal added value.

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 short, front-loaded clause with the endpoint literal first. Nothing is wasted, though there is little substance to be concise about.

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 no-param read with no output schema there is no return-value obligation, and annotations cover safety. Still, the description leaves the agent guessing what 'debug info' contains and whether it is a raw passthrough versus structured data, which a short phrase could have fixed.

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 takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The empty schema with additionalProperties=false is consistent with the description's no-argument nature.

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?

Names the endpoint ``/sys/debug`` and characterizes the payload as device-wide debug info, which implicitly contrasts with the tuner-scoped sibling hdhomerun_get_tuner_debug. However, the verb is only implied and the phrase is so terse that an agent gets scope but not much else.

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 statement of when to call this versus hdhomerun_get_tuner_debug or the sys model/version/features tools. The 'device-wide' wording hints at a distinction but never tells the agent to prefer or avoid this tool in any situation.

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