Get user by ID

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

Annotations already state readOnlyHint=true and openWorldHint=true, so base safety is covered. However, the description adds no behavioral depth—it does not mention error handling, response shape, authorization requirements, or the effect of the 'with' parameter. It simply reiterates the operation without new context.

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 zero wasted words, front-loading the core action and target. However, it is so minimal that it merely mirrors the title, offering no additional structured guidance. It is concise but not necessarily well-developed.

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, the description is partially sufficient, but the undocumented 'with' parameter and lack of output schema information leave gaps. Annotations confirm read-only behavior, but the description does not explain what data is returned or how the optional parameter alters the response, which is necessary for correct usage.

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 description must compensate. It only implicitly references the 'id' parameter ('by ID') but gives no detail on the 'with' parameter, which remains entirely unexplained. The description fails to clarify that 'with' might control related data inclusion or output formatting.

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?

Description says 'Get a user by ID' which clearly specifies a single-user retrieval operation with a specific verb, resource, and identifier. It distinguishes from sibling kommo_users_list by explicitly scoping to a single ID rather than a collection.

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?

No guidance is provided on when to use this tool versus alternatives like kommo_users_list or kommo_users_create. There are no stated prerequisites, exclusions, or context cues for selecting this tool over siblings.

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