refine_cloudflow

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it streams progress and returns a result, but lacks detail on whether it modifies the flow in place or creates a new version, and any required permissions. More context would strengthen this dimension.

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 exceptionally concise, consisting of two sentences that cover when to use, what it does, and what to expect (streaming progress, final result). No redundant information.

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 tool with three well-described parameters and no output schema, the description provides adequate context: it covers the core behavior and streaming. It could briefly explain what 'refine' typically involves or what the output looks like, but overall it suffices.

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 schema covers all parameters with descriptions (100% coverage). The description adds minimal extra semantics beyond the schema, such as implying natural language input. Given high schema coverage, the 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?

The description clearly states the tool's purpose: refine or rebuild an existing CloudFlow automation using natural language. It differentiates from siblings like 'trigger_cloud_flow' by focusing on modification rather than execution. However, it could be more precise about what 'refine' vs 'rebuild' entails.

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 indicates when to use the tool ('when the user wants to refine or rebuild'), but it does not provide explicit guidance on when not to use it or suggest alternative tools. For example, it does not mention that 'trigger_cloud_flow' is for executing flows or that 'ask_ava' tools are for general queries.

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