Send Presence

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

Annotations already declare readOnlyHint=false, so it is known to be a mutation; the description adds the context of presence types but omits 'available' and 'unavailable', which may represent global presence rather than chat-specific typing indicators. It does not contradict annotations.

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 a single concise sentence that front-loads the action, resource, and examples with no redundant phrasing. Every word contributes to understanding.

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?

As a simple tool with two parameters and no output schema, the description provides a basic understanding, but it lacks nuance about the meaning of 'paused', the difference between chat-specific presence and global availability, and expected return behavior. Annotations and schema compensate, but the description alone is not fully complete.

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% for both parameters, so the schema fully documents 'number' and 'presence'. The description adds examples of presence values but does not clarify the full enum or differentiate between typing indicators and availability, though the schema covers this.

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 clearly states the tool's function: sending a presence/typing indicator to a WhatsApp chat, with specific examples (composing, recording, paused). This distinguishes it from sibling tools like send_text or send_media, which handle different message types.

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 description implies usage for indicating typing/recording/paused status, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. There is no mention of when not to use it, such as for global availability changes.

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