unifi_sites

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds substantial behavioral details including pagination response shape (offset, limit, count, totalCount), max limit of 200, and a comprehensive filter expression language with functions, combinators, quoting, and escaping rules.

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 well-structured and front-loaded, but contains minor redundancy by repeating the annotation title and using an 'Operations:' header for a single operation. The information density is high, but slightly less crisp than ideal.

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?

With no output schema, the description fully compensates by explaining the paginated response structure. It covers all essential aspects: operation, pagination, filtering, and cloud-mode targeting, making it complete for a list operation with rich filtering.

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?

Although schema coverage is 100%, the description adds crucial semantics for the filter parameter, defining the full filter syntax and escaping rules. This is essential for using filter correctly and far exceeds the schema's minimal 'see tool description' note.

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 'list (Read): List Local Sites' with a specific verb and resource. The tool name 'unifi_sites' and sibling context make it distinct from other UniFi resource 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?

There is no explicit guidance on when to use this tool vs alternatives. The description implies it is for listing sites, but lacks exclusions or alternative tool references. The cross-reference to unifi_consoles for consoleId provides minor contextual guidance.

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