leave_chat

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds no extra behavioral context (e.g., irreversibility, permissions required, or effects on the chat). It merely repeats the action without enriching the agent's understanding beyond the annotations.

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 short sentence, which is concise and free of filler. However, its brevity results in under-specification; it conveys only the basic purpose and lacks useful details, so it does not earn high marks for value per word.

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?

Given that this is a destructive operation with no output schema provided, the description should ideally disclose consequences, required permissions, or any restrictions. It provides none of this, leaving the tool contextually incomplete for a mutating action.

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 includes a required 'chat' parameter with no description, and schema_description_coverage is 0%. The tool description does not mention this parameter at all, leaving the agent entirely without guidance on what format or value to provide (e.g., ID, username, or peer).

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 action ('leave') and the resource type ('channel/supergroup'), which distinguishes it from sibling 'leave_chats' (plural). However, it does not explicitly clarify whether it applies to all chat types or only channels/supergroups, leaving slight ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like 'delete_dialog' or 'leave_chats'. The description simply states the action without contextualizing it against other related tools.

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