unifi_set_client_fixed_ip

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

With no annotations provided, the description carries the full burden of disclosing side effects. It states 'assign' which implies a mutation, but does not explain whether the change is persistent, reversible, or whether it affects the client's DHCP settings. It also does not mention any required client state or potential impacts on the network.

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 a single, straightforward sentence that is front-loaded with the core action and target. There is no unnecessary verbosity or filler, making it extremely concise and easy to parse.

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 the tool's mutating nature, lack of annotations, and absence of an output schema, the description is too sparse. It does not cover return behavior, side effects, parameter explanations, or any caveats, leaving significant gaps for an agent attempting to invoke the tool correctly.

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%, and the description does not mention any of the parameters (mac, ip, use_fixed_ip) or their roles. The tool name hints at the IP and fixed IP concept, but the parameter semantics are entirely left to the schema's bare type definitions, which is insufficient for a 3-parameter tool.

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's function: 'Assign a static/fixed IP address to a client device on the network.' It uses a specific verb (assign), specifies the resource (client device), and the target (IP address), making it distinct from sibling client tools like unifi_set_client_name or unifi_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?

The description implies the tool is used when a fixed IP address needs to be assigned to a client, but it does not provide explicit guidance on when to use it versus alternatives, nor does it mention any prerequisites or edge cases. The purpose is clear enough to infer basic usage, but there is no explicit when/when-not guidance.

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