unblockClient

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

The destructiveHint annotation already signals this is a mutating action. The description adds the behavioral outcome of restoring network access, but does not disclose potential side effects, failure modes, or whether the operation is idempotent. This is acceptable given the annotation coverage.

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?

A single sentence conveys the action, target, method, and result with no filler. Every word contributes meaning, and the core action is stated first.

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 simple, single-required-parameter tool, the description captures the essential context: the target client, the action, and the outcome. The only notable gap is the lack of any guidance about the optional siteId parameter, but this does not severely impair correct invocation.

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 correctly identifies clientMac as a MAC address, adding meaning to that parameter. However, it does not mention the siteId parameter at all, leaving its role and optionality unexplained.

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 uses a specific verb ('Unblock'), a clear resource ('a previously blocked client device'), and the method ('by its MAC address') while also stating the effect ('restoring network access'). This clearly distinguishes it from sibling tools like blockClient and updateClient.

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 clearly implies when to use this tool: when a client has been previously blocked and needs network access restored. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to select it appropriately.

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