list_cloud_flows

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value with 'visible' (permission-scoped results) and the caveat that runtime/connection status is not asserted. It does not disclose pagination behavior, ordering, default 'top', or shape of returned records.

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?

A single front-loaded sentence with no filler; the scope and the status caveat both earn their place. It is dense/jargon-heavy but not wasteful.

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?

With no output schema and only two parameters, an agent still lacks the essentials to call it well: what fields come back, whether results are ordered, and what happens when 'top' is omitted. The visibility and status caveats are useful but do not fill that 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 coverage is 50%: environment_profile is documented in the schema, while 'top' has only numeric bounds and no description. The description says 'bounded list' but never explains what 'top' means, its default, or that results are truncated at that count, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Read a bounded list of ... cloud flow records') and scopes it to an Online Dataverse environment. It is distinguishable from sibling get_cloud_flow / list_cloud_flow_runs, though it never names those alternatives explicitly.

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 clause 'no runtime or connection status asserted' implicitly steers an agent away from using this for status checks, hinting that list_cloud_flow_runs or connection tools are the right choice. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative.

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