create_evolution_instance

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

Given no annotations, the description carries the transparency burden. It discloses that it creates an instance and returns a hash/apikey and QR code (for Baileys), but does not mention potential side effects, permission requirements, or behavior on duplicate instance names.

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 extremely concise at two sentences, front-loading the core purpose and key outputs. Every word serves a purpose without extraneous detail.

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?

For a tool with 11 parameters and no output schema, the description is too brief. It does not explain the meaning of integration types, boolean flags, or the structure of returned data, leaving significant 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 description coverage is low (36%). The description does not explain any of the 11 parameters, nor does it provide context for the required instanceName or optional fields. It fails to compensate for the low schema 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 ('Create') and the resource ('a new WhatsApp instance'), and distinguishes from sibling tools like connect_evolution_instance or delete_evolution_instance by specifying the return values (hash/apikey and QR code).

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 is provided on when to use this tool versus alternatives, nor are there any prerequisites or exclusions mentioned. The description simply states what it does without context.

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