WAzion MCP Server

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

No annotations provided, so description carries full burden. Successfully discloses mutation nature, confirmation requirement for dangerous actions, and state validation (pending only). Does not mention error behavior if message is not pending or side effects.

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?

Slightly redundant opening ('Update scheduled message — Updates...'), but every subsequent sentence earns its place: capabilities, constraints, and safety requirements. Front-loaded with essential constraints. Minor deduction for mixed language (Spanish safety note) without clear structural separation.

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 100% schema coverage and no output schema, description adequately covers the tool's complexity: mutation marker, confirmation safety gate, editable fields, and state restrictions. Sufficient for agent selection and invocation planning.

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?

Input schema has 100% description coverage, establishing baseline of 3. Description adds semantic mapping ('text, datetime, and/or sending session' correlates to message_text, scheduled_at, session_id) and emphasizes the confirmation parameter's purpose, but largely follows schema definitions.

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 specific verb ('Updates') and resource ('pending scheduled WhatsApp message'), and distinguishes from siblings via the 'Only pending messages can be edited' constraint, clearly differentiating it from create_scheduled_message and cancel_scheduled_message.

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?

Provides clear usage constraints ('Only pending messages can be edited') and critical safety requirements ('requiere confirmación: pasar confirm=true'). Lacks explicit naming of sibling alternatives like create_scheduled_message for new messages.

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