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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the safety profile. The description adds the 'draft' restriction and the error-handling behavior ('Validation errors come back listed'), but the latter is largely repeated in the flowJson schema description. Adds some value, not rich context.

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 compact sentences with no waste. The replace semantics and format requirement are front-loaded in the first sentence, with error behavior appended.

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?

No output schema exists, and the description notes validation errors are returned, which is useful. However, for a destructive mutation tool it omits prerequisites (flow must be in draft) and does not clarify what 'replace' fully discards, leaving gaps.

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 100%, so all four parameters (including idempotencyKey) are already documented in the schema. The description adds no format or syntax detail beyond what the schema provides, so baseline 3 is appropriate.

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: 'Upload (replace) the Flow JSON of a draft flow'. The parenthetical clarifies the replace semantics and 'draft flow' constrains the target. It does not explicitly name a sibling (e.g., create_whatsapp_flow), so differentiation is only implicit.

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?

The 'draft flow' qualifier implies this applies to flows not yet published, but there is no explicit when-to-use, prerequisite, or comparison against siblings like create_whatsapp_flow or validate. Usage must be inferred.

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