dataflow_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds modest behavioral context by stating 'all' (no filtering) and 'Gen2' (item-type scope), but it discloses no further traits such as pagination, ordering, response shape, or failure behavior. There is no contradiction with the annotations.

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?

One eight-word sentence that front-loads the verb and resource, with zero filler or repetition. Every word contributes meaning, and there is no extraneous 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?

For a simple one-parameter list operation with annotations covering the safety profile, the description is nearly complete: it names the operation, resource type, and target workspace. Since there is no output schema, the return format is not stated, but for a list operation the result is self-evident, making this a minor omission rather than a functional gap.

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 description coverage is 100% — the single required parameter workspaceId is already documented as 'The workspace ID' in the schema. The description adds no additional parameter semantics, so the baseline of 3 applies per the rubric.

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 uses a specific verb ('List'), names the exact resource ('Dataflow Gen2 items'), and scopes it ('in a workspace'). The 'Gen2' qualifier removes ambiguity about item type and cleanly distinguishes it from sibling tools like dataflow_get, dataflow_create, and dataflow_delete, as well as from other *_list tools targeting different resource types.

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 intended use is inferable — call this to enumerate all Dataflow Gen2 items in a workspace — but the description provides no explicit guidance on when to prefer it over alternatives such as dataflow_get or other *_list siblings. No exclusions, fallback conditions, or alternative-routing hints are stated; the pattern of sibling list tools implies the usage rather than spelling it out.

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