unifi_block_client

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

With no annotations provided, the description describes the core behavior (prevents connection to any SSID). However, it does not disclose side effects like disconnecting existing sessions or persistence.

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?

Two sentences, front-loaded with the primary action and effect. The second sentence provides a critical sibling reference. No extraneous information.

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?

No output schema exists, but description doesn't explain return values. It differentiates from the unblock sibling but not from other similar tools like unifi_kick_client. Adequate for a simple tool but lacks some behavioral and parameter detail.

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 description must compensate. It clarifies the 'mac' parameter (by MAC address) but does not mention 'site_id', leaving its purpose and default value 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?

Clearly states the verb 'block' and resource 'client by MAC address', and explains the effect of preventing connection to any SSID. Differentiates from sibling tools like unifi_unblock_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?

Explicitly mentions the reverse tool unifi_unblock_client, guiding when to use the alternative. Does not provide explicit when-not-to-use scenarios, but the purpose is clear enough.

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