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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Nothing changes' clearly communicates that this is a non-mutating preview, and 'Call first' indicates sequencing, though it does not cover permissions, error conditions, or what happens after previewing.

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 three short sentences, front-loads the tool's purpose, and every sentence adds useful information: what is shown, that nothing is changed, and that it should be called first.

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 preview tool with no annotations and no output schema, the description supplies the essential behavior and gives examples of returned details. It could be slightly stronger by explicitly naming disconnect_telegram_bot as the follow-up, but no critical information for calling it is missing.

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 required parameter has 100% schema description coverage, already explaining that it is the agent id (UUID) from list_agents. The description does not add any further parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: it shows which Telegram bot would be detached from an agent and lists the relevant details (username, chats, messages). It clearly distinguishes this preview from the actual disconnect operation by saying 'Nothing changes. Call first.'

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 phrase 'Call first' establishes that this should be used before the actual disconnect, giving clear usage context. However, it does not explicitly name disconnect_telegram_bot as the follow-up action or state when not to use this preview.

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