unifi_gen_getmclagdomain

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

The annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds nothing beyond that — not what happens when the ID is unknown, not the error shape, and not the (likely Unifi-API-backed) authorization context implied by openWorldHint.

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 short sentence with the resource front-loaded, plus a compact provenance reference. There is no filler, though the versioned docs URL adds little for an agent deciding how to call the tool.

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 tool whose annotations carry the safety profile, this is minimally sufficient. The remaining gaps — how to obtain the ID and which of several lookalike MC-LAG tools to use — are real but not fatal.

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 0%, and the description never mentions mcLagDomainId, so it does nothing to compensate. An agent gets the UUID format from the schema but no hint that the value should be sourced from the MC-LAG domain list endpoint.

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 states a specific verb and resource ("Get MC-LAG Domain"), so an agent knows exactly what kind of object is retrieved. It does not, however, distinguish this from the near-identical siblings unifi_net_get_mclag_domain and unifi_gen_getmclagdomainpage, leaving the agent to guess which retrieval variant to call.

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 when-to-use guidance is given: no prerequisites, no note on where a domain ID comes from, and no exclusion pointing to list_mclag_domains or the net-namespace equivalent. The only extra text is a source URL, which is provenance rather than usage instruction.

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