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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds genuinely non-annotated behavior: a disabled chatbot_enabled flag suppresses all firing, and pending activation or change requests surface in the result. The enumeration of returned fields is somewhat redundant with the existing output schema.

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?

Three sentences, front-loaded with what is listed and scoped to the organization; no filler. The middle sentence is a long run-on enumerating result fields that the output schema already declares, which costs it a point.

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?

Zero parameters, full annotation coverage, and an output schema mean the remaining burden on the description is scope and the disabled-chatbot caveat, both of which are stated. Nothing an agent needs in order to call this correctly 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 tool takes zero parameters, so the baseline applies and the description cannot add parameter meaning. It stays silent on params without misleading, which is the right call for a no-argument list operation.

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?

Specific verb + resource (lists the AI bots answering WhatsApp customers for this organization) with an explicit scope: the default chatbot plus every rule bot, the latter defined inline as 'an auto-reply rule with an AI persona'. It also names the sibling that covers the non-AI case, so the agent can distinguish list_bots from list_auto_reply_rules without opening either schema.

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?

Explicitly routes the plain (non-AI) auto-reply case to list_auto_reply_rules and warns that nothing fires while chatbot_enabled is false, which is a real usage precondition. It does not say when to reach for get_bot or list_bot_conversations instead of this list, so the sibling routing is only partially covered.

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