get_whatsapp_ai_rules

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

Annotations already mark it as read-only, idempotent, and non-destructive, but the description adds substantial behavior: it explains the null inboundEngagement case, default reply behavior, returned number settings, warnings for silent-AI configurations, and that Meta credentials are never returned.

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 dense and front-loads the core purpose, then adds return-shape and usage details. It is longer than usual, but most sentences carry useful information; minor tightening would improve readability.

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?

With no output schema, the description compensates by describing the returned fields, null semantics, warnings, and credential boundaries. Combined with annotations and the update prerequisites, it gives an agent enough context to call the tool correctly.

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?

There is only one parameter, agentId, but schema description coverage is 0% and the description does not explicitly define it. The context strongly implies agentId identifies the Convocore agent whose rules are read, but the description adds little formal parameter semantics.

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: read the WhatsApp AI rules of a Convocore agent, with the exact decision domain (whether the AI replies to inbound messages) and UI location. It is clearly distinguishable from update_whatsapp_ai_rules and other sibling tools.

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?

It gives an explicit usage rule: call this before update_whatsapp_ai_rules or update_whatsapp_number_settings. That is clear context for when to use it, though it does not spell out when not to use it.

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