evolution_message_send_ptv

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as what PTV entails (e.g., round video, size limits), whether it requires an active instance, or if it works in groups versus individual chats.

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?

A single sentence that is concise and front-loaded, but could be slightly more informative without becoming verbose. It achieves brevity but at the cost of context.

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 output schema, 7 parameters with nested objects, and many sibling tools, the description is insufficient. It does not clarify PTV specifics, required prerequisites, or how quotes/mentions work in context, leaving gaps for an AI agent.

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 100%, so the schema already describes all 7 parameters. The description adds no extra meaning beyond the schema, meeting the baseline for high coverage. No param-specific elaboration in description.

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 sends a PTV (round/instant) video message, using specific verb 'send' and resource 'PTV video message'. This distinguishes it from siblings like evolution_message_send_media (likely for regular video) and other message senders.

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 over alternatives. Among many message-sending siblings (e.g., evolution_message_send_media, evolution_message_send_audio), there is no differentiation or context provided.

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