leaveChat

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does state the success return value ('Returns True on success'), but it does not disclose side effects, failure conditions, permissions, or whether leaving is reversible or has consequences for the bot's membership.

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 extremely concise, with no filler words. The action is front-loaded and the return-value note is a useful addition that earns its place.

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 one-parameter operation with no output schema, the description is largely complete: it states the action and the success return. It could be improved by noting side effects or usage prerequisites, but the schema covers parameter details and the operation is simple.

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 input schema fully documents chat_id, including its allowed types and the @channelusername format, so schema coverage is 100%. The description adds no extra parameter-specific meaning, which is acceptable because the schema already carries the necessary detail.

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, 'Leave', and a specific resource, 'group, supergroup or channel', so the agent knows exactly what operation is performed. It also notes the success return value, which distinguishes it from unrelated chat-management siblings like deleteChatPhoto or sendMessage.

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 intended use is implied by the verb 'Leave' but no explicit when-to-use or when-not-to-use guidance is provided. No alternative tools are named, and there is no mention of prerequisites such as the bot needing to be a member of the chat.

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