waha_send_status

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a 'Post' operation, implying a write action, but doesn't clarify if this requires authentication, what happens on failure, whether it's rate-limited, or if it affects other users. This leaves significant gaps for a mutation tool.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, 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 this is a mutation tool (implied by 'Post') with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after posting (e.g., success response, error handling) or contextual details like platform-specific behavior (e.g., WhatsApp status vs. story), leaving the agent with insufficient information.

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%, with both parameters ('text' and 'session') clearly documented in the schema. The description adds no additional meaning about parameters beyond implying 'text' is for the status content. This meets the baseline score of 3 since 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 action ('Post') and the resource ('a text status/story update'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'waha_send_text' or 'waha_set_presence' which might also involve posting updates, so it doesn't reach the highest score.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'waha_send_text' (for general messages) and 'waha_set_presence' (for presence updates), there's no indication whether this is for WhatsApp statuses, stories, or other specific contexts, leaving usage ambiguous.

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