dataverse_get_cloud_flows

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive. The description adds useful behavioral context by specifying the return of workflow records with statecode, statuscode, and category, and the scoping option. No contradictions with 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?

The description is two sentences, front-loaded with the main purpose, and contains no extraneous information. Every word adds value, making it concise and well-structured.

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 and the presence of rich annotations and an output schema, the description is reasonably complete. It states the return type (workflow records with fields) and scoping options. However, it does not mention pagination or the top parameter, which are relevant for listing.

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?

Despite 0% schema description coverage (tool description does not detail most parameters), the description only covers solution_id and solution_unique_name for scoping. It omits required parameter dataverse_url and optional parameters top, filter, and select, leaving their semantics to the schema alone.

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 tool lists cloud flows in the Dataverse environment, with optional scoping to a solution. The verb 'List' and resource 'cloud flows' are specific, and the description distinguishes this tool from siblings like 'list_processes' by explicitly mentioning 'cloud flows'.

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 provides clear context on scoping with solution_id or solution_unique_name, but lacks explicit guidance on when to use this tool versus alternatives (e.g., list_processes, query_table). It does not include when-not-to-use or compare with other listing tools.

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