Archive / unarchive a chat

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the mutation and local-scope nature are partly covered structurally. The description usefully reinforces 'Local to the account' (no effect on other participants) and implies reversibility via 'or back to the main list,' but it omits idempotency, behavior when the chat is already archived, and error/permission cases.

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 short, front-loaded sentences with no filler; the purpose leads and the scoping caveat follows. The folder-id sentence is compact but introduces a confusing concept that does not correspond to any actual parameter.

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 two-parameter mutation with no output schema, the description covers purpose and the archived/not-archived intent, but leaves the required `chat` identifier format and failure/idempotency behavior undocumented. Adequate but with a clear gap around the mandatory parameter.

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 0% for both parameters. The description spends its only parameter-like detail on a 'folder id' (0 vs 1) that does not exist in the schema, only loosely mapping onto the `archived` boolean, and says nothing about the required `chat` parameter (id vs username vs title). This leaves the required parameter completely unspecified.

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 ('Move a chat into the Archived folder or back to the main list'), which is unambiguous and clearly distinct from siblings like telegram_mute_chat, telegram_pin_chat, or telegram_delete_chat. It stops short of explicitly naming alternatives, but the resource itself is unique enough that an agent can route correctly.

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 when to use it (archiving/unarchiving) and adds the scoping note 'Local to the account,' but offers no explicit when-not conditions, prerequisites, or comparison to alternatives such as telegram_folders. Usage is inferable rather than stated.

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