test_flow

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

The description states 'Execute a flow in test mode with sample inputs,' which implies mutation (write operation), but annotations declare readOnlyHint=true and openWorldHint=true. This is a direct contradiction. Additionally, no behavioral context (e.g., side effects, state changes) is disclosed beyond the conflicting signals.

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 short sentence, which is concise, but it includes a stray '[Write]' marker that reduces clarity. The information density is low, and it could be more structured to convey important context.

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 description fails to explain what the tool returns, whether it runs synchronously or asynchronously, or any behavioral outcomes. Given the lack of an output schema and the tool's complexity (parameters including an object), the description is incomplete for an AI agent to safely invoke the tool.

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 input schema has 100% description coverage, so the parameters are already documented. The description only adds the phrase 'sample inputs' which aligns with the test_inputs parameter, but does not provide additional semantic value or constraints beyond what the schema offers.

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 verb (Execute), resource (a flow), and mode (test mode with sample inputs). It is specific enough to convey the basic purpose, though it does not explicitly distinguish from sibling tools like trigger_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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or how it differs from similar tools like trigger_flow or publish_flow.

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