unifi_set_client_name

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

No annotations are provided, so the description carries the full burden. It only states the basic assignment action. It does not disclose whether the alias overwrites existing names, what happens if the MAC is unknown, permission requirements, or the result/return value. This is a significant gap for a mutation tool.

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, grammatically correct sentence that is front-loaded with the action and contains no redundant phrases. It earns its place with zero waste.

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 the tool's simplicity (2 params, no output schema, no annotations), the description covers the essential purpose and parameter meanings, making it minimally viable. However, it lacks behavioral details like idempotency, error handling, or whether the client must exist, which are important for an agent to invoke it correctly in all scenarios.

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%, so the description must compensate. It does explain that 'mac' is a MAC address and 'name' is an alias/custom display name, which adds meaning beyond the raw parameter names. However, it does not provide format constraints (e.g., MAC notation, name length limits) or clarify behavior when parameters are invalid.

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 (assign), the target (client device), the value (alias/custom display name), and the identifier (MAC address). This unambiguously distinguishes it from sibling tools like unifi_set_client_fixed_ip or unifi_set_client_usergroup.

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 implies when to use the tool: to assign a human-readable name to a client identified by MAC. It does not explicitly mention alternatives or exclusions, but the clarity of 'alias or custom display name' provides sufficient context, with no misleading guidance.

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