getClient

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

With no annotations provided, the description alone must disclose behavioral traits. 'Fetch details' conveys a read operation, but there is no mention of required context such as siteId, error behavior for unknown clients, or whether the result is a single object or nested structure. This is minimal but not misleading.

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 wasted words, which is structurally clean. However, it is under-specified to the point of being terse rather than usefully concise, so it does not earn full credit.

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 tool with no annotations, no output schema, and zero parameter documentation, a one-line description is insufficient. An agent would not know how to format the required clientId, whether siteId is needed for multi-site environments, or what 'details' the response will contain.

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 adds no meaning to either parameter. While 'specific' hints that clientId is the target identifier, it does not explain what siteId is for, whether clientId is a MAC address or internal ID, or any format expectations. The description fails to compensate for the schema's silence.

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 clear verb ('Fetch') and resource ('a specific Omada client'), which is immediately distinguishable from list-oriented siblings like listClients. However, it does not explicitly differentiate its scope from getDevice or clarify what kind of client entity is meant, so it falls just short of a perfect score.

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 guidance on when to use this tool versus alternatives such as listClients, listClientsActivity, or getDevice. The phrase 'a specific' implies the user already has an identifier, but the description does not state that prerequisite or mention any exclusions.

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