Get connected client

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and open-world. The description adds that it applies to connected clients and requires an ID, but it does not explain behavior for unknown/offline clients or what kind of detail is returned.

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 short sentence with no filler. It is concise and front-loads the resource, though it is arguably too sparse for a tool with an undocumented parameter.

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 simple getter this is minimally informative, but with no output schema and no parameter description, the definition should clarify what clientId is and what "detail" covers. The annotations cover safety, but important invocation semantics remain missing.

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 the single clientId parameter is undocumented in the schema. The description only says "by id," which restates the parameter name without specifying format, source, or whether it is an internal ID, MAC address, or other identifier.

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 states a specific operation and resource: retrieving detail for a connected client by ID. It is clear what the tool does, but it does not distinguish itself from nearby siblings such as unifi_net_list_clients or unifi_gen_getconnectedclientdetails.

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 phrase "by id" only implies that the caller must already have a client identifier. There is no explicit guidance on when to use this tool instead of unifi_net_list_clients, unifi_gen_getconnectedclientdetails, or other client-related siblings.

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