validate_flow

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this by stating nothing is saved and that the checks are identical to what create/update enforce, which is behavior the schema cannot express. It also names the errors[] field, valuable since there is no output schema, but never describes that field's shape.

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 key facts are front-loaded, but three of four sentences restate the no-save/dry-run point ('Dry run...', 'Nothing is saved', 'Validate a definition without saving it'). Tightening to two sentences would lose nothing.

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 nested, two-parameter validation tool with no output schema, the description covers the mutation-free nature and the next step but leaves the reader guessing about the errors[] structure and the channels parameter's effect. Adequate to call it, not adequate to call it well.

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 only 50% and the tool takes a deeply nested definition object plus an undocumented 'channels' array. The description says nothing about either parameter, not even that channels scopes which channel-specific rules are validated, leaving a real gap in an otherwise complex 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 ('Validate a flow definition') and immediately disambiguates it as a dry run of the validation that create_flow and update_flow apply, which separates it from those siblings. It does not reach 5 because the same idea is restated three times rather than refined.

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 concrete workflow: loop on errors[] until clean, then call create_flow. That is real when-to-use routing. It stops short of explicitly saying to use this instead of calling update_flow blind, or whether validation is required at all.

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