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

No annotations are provided, so the description carries the full disclosure burden and delivers almost none. It does not say whether resolution is a read-only lookup, what happens when the username does not exist, or whether it hits the network or a cache.

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?

Three words are not concise here but under-specified; the entire description is a label rather than a front-loaded statement of behavior. There is nothing wasteful, but nothing informative either.

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 only one parameter and full schema coverage, the tool is simple, but there is no output schema and 'resolve' leaves the return value undefined. An agent cannot predict whether it gets a user object, an ID, or an error, so the description is not complete enough to call confidently.

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 single parameter has 100% schema description coverage ('Telegram @username to resolve.'), so the schema already fully documents it. The description adds no semantics beyond the schema, which is the expected baseline at high 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 'Telegram: resolve user' effectively restates the tool name and adds only the Telegram namespace. 'Resolve' is an ambiguous verb that could mean lookup by username, resolve to an ID, or hydrate a cached entity, and nothing distinguishes it from siblings like list_dialogs that also return user data.

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 guidance on when to use this versus list_active_chat_participants or list_group_participants, nor any precondition such as needing a known @username. The Telegram prefix is the only contextual signal, which is why it is not a 1.

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