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

Annotations already declare this as a non-read-only, open-world, non-destructive write, so the agent knows the safety profile. The description adds useful evidence-gathering requirements (timestamps with timezone, Meta error code, fbtrace_id, attempts made, business impact), but says nothing about what the call returns, whether tickets can be duplicated, or any rate or size constraints beyond the 20 KB item in the schema.

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?

Two short sentences with zero waste: the purpose is front-loaded and the evidence checklist follows immediately. The parenthetical '(with timezone)' and the named Meta identifiers make the guidance concrete rather than filler.

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 six-parameter, open-world creation tool with a nested diagnostics object and no output schema, the description covers the message content well but omits what a successful call produces (e.g., a ticket reference) and how to set priority or category. It is adequate to invoke the tool but not complete enough to steer escalation decisions.

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 67% schema description coverage, the schema carries most of the load, and the description adds real meaning for the required message field by specifying the evidence it should contain. However, it gives no guidance on choosing category or priority (both enums) or on when to supply waba_id and diagnostics, leaving the discretionary parameters unexplained.

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 opens with a specific verb and resource ('Open a WasapFlow support ticket'), which an agent can distinguish from the sibling read tool bridge_list_tickets. It is clear about what is created but does not name the sibling or state the boundary between listing and opening tickets explicitly.

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?

Usage is only implied: the agent must infer that this tool is for escalating problems to support rather than handling them with the many operational siblings (bridge_call_api, bridge_retry_webhooks, etc.). There is no explicit when-to-use versus when-not-to-use guidance, and no mention of escalation thresholds or prerequisites.

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