Bot: chat info

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world behavior, so the safety profile is covered. The description adds a genuinely useful nuance beyond that: 'as seen by the bot' signals that the returned metadata is scoped to what the bot can perceive, which is not expressible in annotations and matters for a bot-facing lookup.

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?

A single tight sentence with no filler, and the verb and resource are front-loaded before the field list. Every clause earns its place.

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?

With an output schema present, the description need not explain return formats, and the single parameter is fully documented. It covers what is fetched and the bot-relative perspective, though it omits any guidance on failure cases (e.g. chat not found, bot not a member).

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 coverage is 100% and the chat_id description already explains both accepted forms (numeric id sourced from bot_get_new_messages/bot_list_chats, or a '@username' handle). The tool description adds nothing further about the parameter, so the baseline of 3 for a fully-documented schema is correct.

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 gives a specific verb and resource ('Get a chat's type, title or name, username and description') and even enumerates the returned fields, so the agent knows exactly what it retrieves. It does not, however, name or contrast itself against close siblings like bot_list_chats or bot_read_chat, which is the only thing keeping it from 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?

There is no explicit statement of when to use this tool versus bot_list_chats, bot_read_chat, or bot_search_messages. The only routing hint ('number from bot_get_new_messages or bot_list_chats') lives in the schema's chat_id description, not in the tool description, so usage selection is left to inference.

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