Get user

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds no behavioral transparency beyond what is already structured. It does not mention error behavior, response shape, authorization needs, or what happens when the user does not exist.

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 sentence with no filler, repetition, or irrelevant content. It front-loads the core operation and resource immediately, making it easy to scan.

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 single-parameter getter, the description is minimally adequate, but it leaves gaps: no mention of alternatives, no parameter details despite 0% schema coverage, and no behavioral context beyond the readOnly annotation. These gaps make it acceptable but not fully complete.

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 explain the userId parameter beyond the generic phrase 'by id'. While the parameter name is self-explanatory, the description fails to compensate for the lack of schema documentation with any additional detail about format, scope, or constraints.

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 uses a specific verb ('Fetch') and a specific resource ('a single user') with the retrieval criterion ('by id'). It clearly distinguishes this from the sibling ghl_list_users, which would retrieve multiple users, and from other get_* tools targeting different resources.

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 for retrieving one user when the userId is known, but it does not explicitly state when to prefer this over ghl_list_users or any other alternative. There is no exclusionary guidance or explicit when-not-to-use condition.

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