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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description nevertheless reinforces it with 'without publishing or running anything' and then enumerates the actual checks performed (step validity, template references, empty branches, Call Flow target/input/response compatibility, table/field existence). It stops short of describing the failure report format or whether it can be slow on large folders.

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?

Front-loaded with the single most important fact (no publishing, no running) and organized by mode. It is dense with nested parenthetical detail, which is justified by the breadth of checks but does make it one of the longer descriptions.

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 two-parameter validation tool with no output schema, the description covers both invocation modes, the exact scope of checks, and the workflow position relative to ap_lock_and_publish. Nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3, but the description goes beyond the schema by explaining what each parameter's validation mode actually inspects, which is meaningful for choosing between flowId and folderName. It does not add format constraints beyond the schema's minLength/maxLength.

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 (validate) and scope (one flow by flowId, or every flow plus interconnections in a folder by folderName), and immediately distinguishes itself from ap_test_flow and ap_lock_and_publish by clarifying it publishes/runs nothing. An agent can tell it apart from the many other ap_* tools without opening a schema.

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?

Explicitly names the triggers: before ap_lock_and_publish, and after assembling a multi-flow/table solution. It also names the alternative it replaces ('instead of inspecting them by hand') and routes between the two modes (flowId for one flow, folderName for a whole solution).

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