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

The description goes beyond annotations by detailing that the result contains both an image and a specific 'qrLink URL' leading to an 'official GREEN-API page with a full-size auto-refreshing QR code.' This provides rich, non-obvious behavioral context about the output format and reliability.

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 slightly lengthy due to the detailed instructions on markdown formatting, but every sentence is necessary to convey the full operational requirements of the tool.

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?

The description is highly complete. It informs the agent what data to retrieve (image + link), why the link is important (auto-refresh), and how to deliver it (clickable markdown link), leaving no ambiguity for execution or presentation.

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?

With 100% schema description coverage, the baseline is 3. The description only provides contextual clarity (linking the ID to 'instance authorization') rather than explaining the schema itself.

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 its purpose: to 'Get the QR code for instance authorization.' This is highly specific and immediately differentiates it from sibling tools like `whatsapp_connect` or `whatsapp_create_instance`.

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?

While it doesn't explicitly state sequencing (e.g., 'must call this before connect'), it provides a critical usage rule: the agent must 'Always include the qrLink' in its response to ensure user success. This dictates the required presentation of the result.

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