whatsapp_subscribe_chat_presence

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

With no annotations, the description carries full burden but fails to disclose side effects: whether subscription persists, triggers events, or requires specific permissions. The term 'subscribe' implies ongoing behavior but no details.

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?

A single concise sentence that states the core action without waste. However, given the lack of additional context, it might be too brief; a slightly longer description could improve clarity.

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?

The tool has one parameter but no output schema. The description does not mention the return value, such as a subscription ID or confirmation, nor the start of a stream. An agent would need more context to use it 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?

Schema coverage is 100% for the single parameter 'chatId', so the description adds no additional meaning beyond the schema's 'Chat JID'. 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 uses a specific verb 'subscribe' and resource 'presence updates for a chat', clearly indicating the action. It distinguishes from sibling tools like 'whatsapp_set_chat_presence' which sets rather than subscribes. However, it could be more specific about what 'presence updates' means.

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 such as 'whatsapp_set_presence' or 'whatsapp_get_chat'. There are no contextual hints about prerequisites or typical scenarios.

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