whatsapp_set_chat_presence

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

Adds behavior beyond the annotations: the indicator is visible to the other party in real time, it transmits nothing on its own, and the call returns a success confirmation. The idempotent/openWorld safety profile is already carried by annotations, so this is solid supplementary context.

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 short sentences with zero filler; the core action is front-loaded and the caveats follow. Every sentence 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 two-parameter, non-destructive tool with no output schema, the description covers action, audience visibility, side-effect boundary, and return shape. Only the relationship to subscribe_chat_presence is left implicit.

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 description coverage is 100% and the enum values (typing/recording/paused) are documented in the schema. The description reinforces the meaning of 'paused' but adds little syntax or format detail beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb and resource ('Show a typing or recording indicator in a chat') and covers the clearing case ('or clear it with paused'). An agent can tell what it does, though it does not explicitly contrast with the nearby sibling whatsapp_subscribe_chat_presence, which concerns receiving presence rather than sending it.

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?

Gives clear invocation context ('Use it just before sending a reply') and a useful scoping caveat ('it does not send anything by itself'). It stops short of naming alternatives or exclusions, so it is clear but not fully routing-aware.

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