Get VomeHome instance

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. On top of that the description discloses the auth requirement (VOMEHOME_TOKEN) and the nature of the returned data (live status, HA URL), which is meaningful added context for an open-world read.

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?

One compact sentence with the action, scope, and return content front-loaded, followed by the auth caveat. No filler.

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 single-parameter, read-only lookup with no output schema, the description covers what it retrieves and the token requirement. It could be marginally stronger by noting failure behavior for an invalid id, 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 coverage is 100% and the single instance_id parameter is fully documented as a UUID from vomehome_list_instances. The description's 'by id' adds no format or source detail beyond what the schema already provides, so baseline 3 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?

States a specific verb and resource ('Get one VomeHome instance by id') plus what the result contains (live status and the Home Assistant URL). Sibling differentiation from vomehome_list_instances is implied by 'one ... by id' but the sibling is not named explicitly.

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?

Usage is implied (fetch a single instance's details once you have its id from the list tool), and the description states the auth prerequisite ('Requires VOMEHOME_TOKEN'). It gives no explicit when-not conditions or pointer to the alternative tool for listing.

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