flow

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

Explicitly labels the tool as read-only. Describes mutually exclusive parameters and action-specific behavior. Without annotations, the description covers key behavioral traits, though it omits side effects or permissions.

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?

Concise and well-structured: starts with overall purpose, then bullet-like list of arguments. 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?

Covers all 8 parameters, multiple actions, and mutual exclusion. Since an output schema exists, the description sufficiently completes the context needed for invocation.

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?

Adds meaningful explanations for each parameter beyond the schema (e.g., 'mutually exclusive with name', 'gzip+base64+JSON blob'). The schema coverage is 0%, so the description compensates well, though it could clarify default values.

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?

Clearly states the tool inspects Flow Designer flows, triggers, and value blobs in a read-only manner. The description is specific to this tool but does not explicitly differentiate it from siblings like 'query' or 'record_read'.

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?

Provides detailed parameter explanations but lacks guidance on when to use this tool versus alternatives. No explicit when-not-to-use or exclusion conditions.

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