unifi_gen_gethostbyid

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond a source URL — no note on what a 'host' is in this API, what the response contains, or whether an unknown ID errors versus returns empty.

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 very short and front-loads the operation, which is good, but half of the text is auto-generated provenance boilerplate that does not help an agent decide or invoke. Brevity here reflects under-specification rather than disciplined editing.

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?

No output schema exists, so the description is the only place an agent could learn what a host record contains or how to obtain a valid id — and it says neither. For a generated single-entity lookup tool, that leaves a meaningful gap.

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% and the single `id` parameter is documented as 'Unique identifier of the host', so the schema carries the load. The description adds no syntax, format, or provenance detail about where an id comes from (e.g., a listhosts call), 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?

The description restates the tool name almost verbatim ("Get Host by ID") plus a provenance URL, which is essentially tautological against the title. It does convey the verb (retrieve) and the resource (host, keyed by id), but gives no differentiation from siblings such as unifi_sm_get_host or unifi_gen_listhosts.

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 statement of when to use this tool versus alternatives, and the sibling set contains a near-duplicate (unifi_sm_get_host) that an agent would need help disambiguating. No prerequisites, no scope notes, no exclusions.

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