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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the description adds behavioral value by disclosing search behavior, automatic pagination, the paste-ready nature of templates, and the full createdBy object. This enriches the agent's understanding beyond the structured annotation data.

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 dense and front-loaded with the core action before enumerating return fields. The field list is long but earns its place given there is no output schema; the second sentence efficiently conveys search behavior and the downstream integration.

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 read-only list tool with no output schema, the description is complete: it names the primary purpose, all return fields, parameter-specific effects, pagination, environment requirements, and how results feed into update_live_flow. Nothing essential for a correct call is missing.

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?

Input schema coverage is 100%, so the description need not restate parameter basics. It adds meaningful downstream semantics: search triggers addition of connectionReferenceTemplate and hostTemplate, and these can be dropped directly into update_live_flow without edits, which goes beyond the schema text.

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 ('List') and resource ('Power Platform connections'), scoped to an environment and 'directly from Power Automate', which distinguishes it from sibling list_store_connections. The description also enumerates the returned fields, making the tool's purpose concrete and unambiguous.

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 clear context for when to use the tool: pass search to narrow results, call list_live_environments if lacking an environment, and use the returned templates with update_live_flow. It does not explicitly contrast with list_store_connections, but the live-vs-store sibling naming and environment scoping largely carry that distinction.

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