unifi_unblock_client

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

No annotations are provided, so the description must carry the full behavioral disclosure. It only states the action 'unblock' without revealing side effects, whether the operation is idempotent, error cases, or whether it affects the network state beyond unblocking. This is insufficient 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 sentence, front-loaded with the action, and contains no unnecessary details. It is efficient and to the point.

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?

The tool is simple with one parameter and no output schema. The description covers the core action and parameter meaning, but it lacks context about prerequisites (e.g., what happens if the client is not currently blocked) and does not differentiate from reconnect in ambiguous 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?

The schema has 0% description coverage, but the description explicitly states 'by MAC address', which fully explains the meaning of the single 'mac' parameter. This compensates for the lack of schema descriptions.

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 tool's function: 'Unblock a previously blocked client device on the network by MAC address.' It uses a specific verb+resource structure and distinguishes itself from sibling tools like unifi_block_client and unifi_reconnect_client.

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 the tool is used when a client device has been previously blocked and needs to be resumed. However, it does not explicitly state when to prefer this over alternatives, nor does it provide exclusions or prerequisites beyond the implicit 'previously blocked' condition.

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