unifi_gen_executeconnectedclientaction

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description itself adds nothing about what gets destroyed, whether authorization is reversible, or that a confirm/dry-run preview flow exists (that only appears in the schema). The docs link is the sole added value.

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?

It is a single short line with no padding, and the verb+resource is front-loaded. However, the brevity comes from under-specification rather than economy, and the only substantive content is the appended URL.

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 on a client with a 4-parameter body and no output schema, an agent needs to know what the action does and what the response/preview looks like. The description supplies neither, leaving annotations and schema to carry nearly everything.

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 75% — body, confirm and dry_run all carry inline descriptions explaining preview-vs-apply behavior, so the schema does the heavy lifting. The description contributes no parameter meaning beyond that, and clientId is undocumented, keeping this at the baseline for a mostly-covered schema.

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 restates the tool name ("Execute Client Action") and appends a vendor docs URL, adding essentially no explanatory content. It does not say what the action does, what action types exist (only the schema enum reveals AUTHORIZE_GUEST_ACCESS / UNAUTHORIZE_GUEST_ACCESS), or how it differs from close siblings like unifi_net_client_action or unifi_net_block_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?

There is no when-to-use guidance and no mention of alternatives, despite the sibling list containing several overlapping client-manipulation tools (unifi_net_client_action, unifi_net_block_client, unifi_net_unblock_client). The only implied usage cue is the linked vendor documentation page, which the agent would have to fetch separately.

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