Execute client action

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds one genuinely useful behavioral fact (the Network API exposes no block/unblock action, preventing a wrong call), but says nothing about the mutation's consequence, reversibility, or the confirm-gate/preview behavior.

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?

Three compact sentences, front-loaded with the resource and action vocabulary, followed by the normalization hint and a negative constraint. No padding or repetition of schema content.

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 destructive, non-idempotent mutation with no output schema, the description leaves the agent without return-value expectations or a statement of what the action actually changes on the client. The critical preview/confirm gating exists only in parameter descriptions, so a reader of the prose alone could issue a live change unintentionally.

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?

With 0 enums in the schema, listing AUTHORIZE_GUEST_ACCESS and UNAUTHORIZE_GUEST_ACCESS in prose is real added value, and the note that lowercase/dash forms are normalized tells the agent it need not over-normalize input. The confirm and dry_run parameters are not addressed in the description, but the schema documents them at 75% coverage, so the baseline is satisfied.

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?

States a specific verb+resource ('Action on a connected client') and enumerates the two supported vendor action values, which distinguishes it from the get/list client siblings. However, it does not name its closest sibling (unifi_gen_executeconnectedclientaction) or explain how the two differ, so differentiation is only partial.

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 use case (guest-access authorization/deauthorization on a client) and usefully notes that block/unblock is not available through this API, implicitly routing the agent to unifi_net_block_client/unblock_client. There is no explicit when-to-use vs the sibling action tool and no mention of the confirm/dry_run workflow the schema requires.

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