get_chat_info

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

With annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds the scope of 'any entity' but does not add further behavioral context such as authentication requirements or rate limits. Since the annotations cover the safety profile, a middle score is appropriate.

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, front-loaded sentence that communicates the core purpose without redundancy. Every word is purposeful, and it is 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?

Given the tool's low complexity (one parameter, no nested objects, and an output schema present), the description is mostly sufficient. It states the main function and entity scope, while the output schema handles return value details. Missing usage guidance slightly reduces completeness, hence a 4.

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 provides a single 'chat' parameter of anyOf integer/string, and the description adds that it works for any user/chat/channel/bot, clarifying semantic scope. However, it does not explain acceptable formats (e.g., username vs. ID), so the description only partially compensates for the 0% schema coverage.

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 that the tool provides detailed information about any entity (user/chat/channel/bot). It uses a specific verb ('get') and resource ('entity info'), which makes the purpose understandable. However, it does not explicitly differentiate from sibling tools like get_full_user, so it stops short of a 5.

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 used when you need entity details, but it provides no explicit when-to-use guidance or alternatives. There is no mention of situations where other tools (e.g., get_full_user) would be more appropriate, leaving the agent to infer usage.

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