telegram-terminate-session

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

Annotations already mark the tool as destructive (destructiveHint=true). The description adds value by clarifying that terminateAllOther excludes the current session, which is not obvious from annotations alone. It does not disclose further side effects, but the safety profile is adequately covered.

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 concise sentence covering both use cases without any unnecessary words. Efficient and front-loaded.

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?

The description is sufficient for a simple termination tool with clear annotations. It does not mention error handling or return values, but given the tool's straightforward nature and the presence of exhaustive sibling context, it is reasonably complete.

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?

With 100% schema coverage, the description still adds significant meaning: it notes that sessionId comes from get-sessions and explains that terminateAllOther excludes the current session, providing context beyond the schema descriptions.

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 verb 'terminate' and the resource 'Telegram session', specifying two distinct modes: by hash or all other sessions. It effectively distinguishes this tool from siblings like telegram-get-sessions or telegram-logout.

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 explicitly indicates when to use each parameter (sessionId for specific termination, terminateAllOther for all others), and implies that the current session is excluded. It lacks explicit 'when not to use' instructions but is clear enough for correct invocation.

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