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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low, yet the description adds real disclosure: the exact scope of returned data, the deliberate exclusion of handlers/config/bindings, and the truncation behavior for very large flows ('shortened and says so'). It does not mention permissions or auth requirements, but those are minor here.

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?

Three tight sentences, zero padding, and the core payload description is front-loaded before the exclusions and truncation caveat. Every sentence carries information the agent needs.

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?

With no output schema, the description must carry the return contract, and it does so thoroughly: what is present, what is deliberately absent, and how oversized flows are handled. An agent can set expectations correctly before calling.

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 50% and the description never references the optional 'fields' selector, which is the parameter most in need of guidance for this tool. It does describe the record contents (screens, wording, compliance) at a high level, but adds no syntax or usage detail beyond the schema.

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 a specific verb+resource ('Read one WhatsApp Flow') and even enumerates the returned payload (screens, component wording with JSON pointers, compliance report summary). The singular 'one' implicitly separates it from list_whatsapp_flows, but no sibling is named, so differentiation is left to inference.

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?

Gives a clear use context by declaring what is NOT returned ('the endpoint configuration, handlers and bindings are not'), which effectively tells the agent when to look elsewhere. It stops short of naming an alternative tool for that content, so no explicit routing is provided.

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