get_flow

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

No annotations provided, so description carries full burden. It mentions 'normalized editable payload' implying transformation, but does not state if data is read-only, whether it triggers side effects, or if authentication/perms are needed.

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?

Single sentence, front-loaded with verb and resource. Efficient but could benefit from a brief note on prerequisites or output format without bloating.

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 no output schema and complex nested input, description should explain what 'normalized editable payload' entails (e.g., structure, fields). Lacks guidance for a tool with many siblings, making it hard for agent to determine suitability.

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 0% as descriptions in schema are just field names. Description adds 'selected Power Automate flow target' but does not explain envId or flowId meaning, format, or how to obtain them. Leaves agent to infer from context.

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?

Verb 'Fetch' and resource 'Power Automate flow target' are clear. Output described as 'normalized editable payload' adds specificity. However, no explicit differentiation from siblings like get_run or get_context, though the target flow is distinct.

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 on when to use this tool versus alternatives (e.g., list_flows for enumeration, get_run for run details). No context on prerequisites or selection criteria.

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