Check discovery cache freshness

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, which is counterintuitive for a 'check' operation, yet the description adds nothing to clarify what mutation or side effect occurs. It repeats the annotation title verbatim rather than explaining behavior, so it earns no credit beyond the structured fields.

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 sentence, but its brevity comes from under-specification rather than efficiency. The one sentence present conveys no information an agent could not get from the tool name, so it does not earn 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?

Despite an output schema existing, an agent still cannot tell what the cache is, what 'freshness' measures, why the operation is marked non-read-only and open-world, or how it relates to discovery_operations_cache. For a tool with a surprising annotation profile, this description is wholly inadequate.

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, and the description makes no false claims about inputs. With no parameters to document, there is nothing the description could add, so the baseline for a zero-param tool applies.

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 restates the tool name/title as 'Invoke the check_discovery_cache_freshness operation' without saying what is actually checked, what 'freshness' means, or what happens as a result. It is essentially a tautology and gives no differentiation from siblings like discovery_operations_cache or hdhomerun_get_discover.

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 guidance on when to call this versus the many discovery-related siblings (discovery_operations_cache, hdhomerun_discover_cloud, hdhomerun_discover_local_broadcast, hdhomerun_get_discover). No prerequisites, no exclusions, nothing an agent could use to choose this tool.

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