whatify_send_flow

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

No annotations provided, and the description gives zero behavioral context: no mention of success/failure behavior, error handling, authentication needs, rate limits, or what happens on invalid inputs.

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, but it omits essential details, making it under-specified for a tool with no annotations and multiple parameters.

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 the lack of annotations and output schema, and the presence of sibling send tools, the description fails to provide complete context for correct invocation, such as expected behavior, return format, or integration details.

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 coverage is 75% with descriptions for phone (format), flow_id (alternative value), and flow_cta (default). The tool description itself adds no additional value beyond the schema's param descriptions, meeting the baseline for high coverage.

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 (Send), the resource (WhatsApp Flow), and the target (to a phone number via Whatify). It effectively distinguishes from sibling tools like send_message and send_template by specifying 'flow'.

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?

No guidance on when to use this tool versus alternatives (e.g., send_message, send_template). No prerequisites or when-not-to-use conditions are mentioned.

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