waha_get_presence

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

With no annotations provided, the description carries the full burden. It discloses the auto-subscription behavior, which is valuable beyond basic functionality. However, it lacks details on permissions needed, rate limits, error conditions, or what the return format looks like (e.g., structured data or simple status).

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, efficient sentence that front-loads the core purpose and adds the auto-subscription detail without waste. Every word earns its place, making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is moderately complete. It covers the tool's purpose and a key behavioral trait (auto-subscription), but lacks details on return values, error handling, or prerequisites. For a tool with 1 parameter and 100% schema coverage, it's adequate but has clear gaps in behavioral context.

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%, so the schema already fully documents the chatId parameter. The description doesn't add any meaning beyond what's in the schema (e.g., it doesn't clarify format beyond 'number@c.us' or provide examples). Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Get online/offline/typing status') and resource ('for a chat'), distinguishing it from sibling tools like waha_get_all_presence (which gets presence for all contacts) and waha_set_presence (which sets presence). It precisely defines what the tool retrieves.

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 provides clear context for when to use this tool by mentioning 'Auto-subscribes if not already subscribed,' which implies it's for monitoring a specific chat's presence. However, it doesn't explicitly state when not to use it or name alternatives like waha_get_all_presence for broader monitoring.

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