unifi_update_known_client

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

No annotations are present, so the description must fully disclose behavior. It states 'Update' which implies mutation, but fails to mention side effects, required permissions, or what happens to unspecified fields. Only the `blocked` parameter's effect is elaborated minimally.

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 concise with two sentences, no redundancy. It front-loads the purpose and lists typical use cases. However, it could be better structured with separate sentences for each field explanation.

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?

Given 7 parameters, no output schema, no annotations, and many sibling tools, the description is incomplete. It lacks information on return values, required authorizations, and full parameter documentation, making it insufficient for an AI agent to confidently use this tool without additional context.

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% (no descriptions in the schema). The description adds meaning for `client_id`, `name`, `note`, `blocked`, and `fixed_ip`, but leaves `site_id` and `use_fixedip` unexplained. With 7 parameters and no schema documentation, the description should cover all parameters but does not.

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 updates a known client record by its _id and lists common uses like setting a friendly name, blocking/unblocking, and assigning a fixed IP. However, it does not explicitly distinguish from similar tools like `unifi_block_client` or `unifi_unblock_client`, which could cause ambiguity for an AI agent.

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 provides common use cases but lacks explicit guidance on when to prefer this tool over alternatives (e.g., using `unifi_block_client` for a simple block). It does not mention preconditions or when not to use this tool.

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