Get user

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Get' and 'single...by id' convey a read-only, one-record lookup, but the description does not mention possible 404 behavior, required authorization, or the shape of the returned user. This is acceptable for a simple getter but not richly transparent.

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, front-loaded sentence: 'Get a single user by id.' Every word adds relevant information and there is no filler or repetition.

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 get-by-id tool with one parameter, the description is close to adequate. However, there is no output schema and no mention of what the response contains or what happens when the user does not exist, so the contextual picture is 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?

The schema has no parameter descriptions, but the description clarifies that the sole parameter, userId, is the id of the user to retrieve. This adds some meaning beyond the bare schema, yet it does not explain id format or any constraints, leaving the parameter semantics minimally viable.

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 verb and resource: 'Get a single user by id.' The word 'single' distinguishes it from list-style tools like gambot_list_users, and it is clearly scoped to the user resource rather than the many other get_* siblings.

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 when to use it: when a single user is needed by id. However, it does not explicitly mention alternatives like gambot_list_users for fetching multiple users or gambot_get_contact for non-user lookups, so the usage guidance is merely implied rather than stated.

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