resolve_chat

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

The description mentions caching as a behavioral trait but does not disclose whether the operation is read-only, requires authentication, or failure modes. With no annotations, this is insufficient.

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, 12-word sentence that is highly concise and front-loaded with the verb 'Resolve'. No wasted words.

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 tool with no output schema and no annotations, the description provides minimal context. It lacks details on return values, error conditions, and typical usage flow, making it incomplete for an agent.

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 input schema already describes both parameters with complete descriptions. The tool-level description adds overall context but no additional parameter-specific meaning. Baseline 3 is appropriate given 100% 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 the action ('resolve' and 'cache') and the resource ('Telegram chat' and 'input peer'). It distinguishes from siblings like get_chat_info by specifying caching behavior, though the term 'input peer' may be jargon.

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 on when to use this tool versus alternatives such as get_chat_info. No prerequisites or when-not-to-use information. The agent must infer usage from context.

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