protect_list_ulp_users

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, but the description adds value by confirming the read nature and disclosing that enrolled-credential details are not exposed. This goes beyond what annotations provide. No other behavioral aspects (e.g., pagination) are mentioned, but given the tool's simplicity, this is sufficient.

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 two sentences with no wasted words. The first sentence clearly states the purpose, and the second provides essential details. It is front-loaded and efficient.

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 zero-parameter list tool with an output schema available, the description covers the core purpose, return structure, and known limitations. It implicitly assumes the agent can handle the output schema for format details. Could be slightly enhanced by mentioning ordering or default count, but current level is adequate.

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?

There are no parameters (schema coverage 100% by default), but the description compensates by explaining the output structure and limitations. It specifies the exact fields returned and explicitly states what is excluded. This fully informs an agent of the tool's capabilities.

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 explicitly states 'List all UniFi Identity (ULP) users' with a specific verb and resource. It further details what each user includes (id, modelKey, etc.) and what is NOT exposed, leaving no ambiguity about the tool's function. The distinct resource type 'ULP users' differentiates it from sibling 'list_users' 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?

The description provides context about returned fields and explicitly excludes credential detail, helping agents set expectations. However, it does not mention when to use this tool versus alternatives like protect_get_ulp_user for a single user. No explicit usage conditions or exclusions are stated.

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