Run a fresh health check

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

Goes well beyond the readOnlyHint=false / openWorldHint=true annotations: it discloses the couple-of-minute latency, that the new report replaces the old one, that write access is required, and that an unlinked home gets a temporary link deleted after a day unless someone signs in. These are exactly the operational traits an agent needs before invoking a mutating, slow, open-world call.

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?

Front-loads the action and the key scoping fact (report replacement), but the trailing clause 'vome_health_check runs a first check' restates the name and adds little. Mostly dense, with one mildly redundant sentence.

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 tool with no output schema, it covers latency, side effects on the existing report, permissions, and how to retrieve results. It could be slightly clearer about what the call itself returns immediately, but nothing essential is missing.

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?

Schema description coverage is 100%, so both parameters (use_ai, instance_id) are already fully documented in the schema; the description adds no meaning about either. Baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Start a fresh Vome health check on this Home Assistant') and clearly separates itself from the read-side sibling by directing report reading to vome_health_report. An agent can distinguish it from vome_health_report and ha_check_config without opening either schema.

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?

Gives a clear triggering context ('after fixing findings, this is how the score catches up') and names the follow-up tool (vome_health_report). It also states the integration prerequisite and the not-yet-linked case, though it offers no explicit 'do not use when...' exclusion.

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