set_flow_meta

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only says 'Update', implying mutation, but does not specify side effects, idempotency, error conditions, or whether fields are overwritten. The description also fails to mention that it likely modifies metadata only, not structural elements like steps. This is a significant transparency gap.

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 description is a single, compact sentence that is front-loaded with the action and target. It contains no filler and conveys the essential information efficiently, earning a perfect score for conciseness.

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?

The tool has 7 parameters and no output schema, so the description must provide sufficient context for correct invocation. It fails to mention return values, prerequisites (e.g., flow existence), error behavior, or how the update affects existing data. Given the tool's complexity, the description is incomplete and leaves critical details unspecified.

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?

The description lists the updatable fields (name, folder, description, preconditions, notes), adding meaning beyond the bare schema types. However, it does not explain each parameter's format or constraints (e.g., whether preconditions is a string or expression). Since schema description coverage is only 14%, the description partially compensates but could provide more detail on parameter semantics.

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 states a specific verb ('Update') and resource ('a flow'), and explicitly lists the fields it modifies (name, folder, description, preconditions, notes). This clearly distinguishes it from sibling tools like create_flow and delete_flow, which have different actions. It fully communicates the tool's scope.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for updating existing flows, nor does it exclude cases like creating a flow (create_flow) or modifying steps (update_step). An agent must infer usage from context, which is insufficient given the many sibling tools.

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