get_user_info

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

No annotations are provided, so the description must cover behavioral traits. It indicates a read operation but does not mention permissions, error behavior (e.g., if user not found), or any side effects. For a simple lookup, the transparency is adequate but not fully detailed.

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 extremely concise: two short sentences with a front-loaded tag [User Identity]. Every word serves a purpose, and there is no unnecessary content.

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 lookup tool without an output schema, the description sufficiently conveys the input and outcome. It does not detail the return format, but given the tool's simplicity and common pattern, it is mostly 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 100%, with both parameters described. The description adds minimal value beyond the schema: it reinforces the user_id parameter by saying 'by user ID' but does not clarify the optional chat_id parameter further. Baseline 3 is appropriate.

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 clearly states the tool's purpose: looking up a user's display name by user ID. The verb 'look up' and resource 'user's display name' are specific, and the tool is distinct from sibling tools like get_chat_info or get_login_status.

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 usage for simple user lookups but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context is clear but the guidelines are missing.

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