Sign out of Telegram

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

The description adds meaningful context beyond the annotations: it clarifies that the action affects both the local session ('Drop the local session') and the server-side session ('revoke it on the Telegram side'). This goes beyond the generic destructiveHint and provides specific behavioral detail about the scope of the side effects.

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, concise sentence that conveys the essential behavior without any fluff. It is front-loaded with the core action and uses precise language, making it easy for an agent to quickly understand the tool's purpose.

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 one-parameter logout tool with annotations, the description is nearly complete. It covers the local and server-side effects, and the remaining missing detail (return value) is not critical given the tool's simplicity. The absence of an output schema also reduces the need to describe return values, but a note on success/failure signaling might have been useful.

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 covers 100% of the parameter documentation, including the key detail that accountId comes from listAccounts. The tool description itself does not add any parameter-level information, which is acceptable given the high schema coverage, but it also doesn't clarify any edge cases or usage nuances beyond the schema.

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 tool's function: 'Drop the local session for an account and revoke it on the Telegram side.' This is a specific verb+resource (drop/revoke session) that distinguishes logout from siblings like login or list_accounts, which involve creating or listing sessions.

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 usage context is implied by the title and description: use this to sign out an account. However, there is no explicit guidance on when to use this tool vs alternatives, nor any mention of exclusions or prerequisites. The description assumes the user knows when to call it.

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