test_flow

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

Annotations already indicate the tool is not read-only and not destructive. The description adds '[Write]' which is redundant with readOnlyHint=false. The term 'test mode' suggests limited side effects, but no concrete behavioral traits (e.g., what gets modified, required permissions, or rollback behavior) are disclosed.

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 concise sentence followed by a useful marker ('[Write]'), indicating efficient use of space. However, it could be slightly restructured to include guidance on usage without sacrificing brevity.

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?

Given the tool's complexity (two parameters, one nested object) and no output schema, the description should explain what the tool returns or what 'test mode' entails (e.g., whether results are persisted). The description is too sparse to fully inform an agent, and the 'test_inputs' parameter lacks guidance on format.

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 both parameters ('flow_sys_id', 'test_inputs') have descriptions in the schema. The description does not add any additional parameter-level information, meeting the baseline expectation for a fully covered 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?

The description clearly states the action ('Execute a flow'), the specific mode ('in test mode'), and the type of inputs ('with sample inputs'). It effectively distinguishes this tool from siblings like 'trigger_flow' (presumably for production) and 'publish_flow'.

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 implies the tool is for testing flows, but does not explicitly state when to use it versus alternatives (e.g., 'trigger_flow' for production). No when-not-to-use or prerequisites are mentioned, leaving selection guidance implicit.

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