unifi_list_sites

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

The description implies a read-only listing operation with no side effects, appropriate for a list tool. However, no explicit statement about mutability, destructive potential, or permissions is provided, and there are no annotations to supplement this.

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?

The description is a single concise, front-loaded sentence that efficiently conveys the tool's purpose without extraneous words. Every word earns 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?

Given no output schema, the description provides the expected output fields (UUID and name). However, it lacks context on pagination behavior, rate limits, or any unique characteristics compared to sibling list tools, which are many.

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 description adds no extra meaning beyond the schema's own parameter descriptions. The tool's description does not explain how limit, filter, and offset apply specifically to sites, so the value added is minimal.

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 clearly states the action ('List'), the resource ('local sites'), and what is included ('UUID and name'). It distinguishes from sibling tools by specifying 'local sites' rather than a generic resource, but does not explicitly differentiate from similar list tools.

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 is provided on when to use this tool versus alternatives. It does not mention any prerequisites, scenarios, or conditions for use, nor does it offer when-not-to-use advice.

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