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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description is free to add behavioral details without redundancy. It does so by explaining the effect of each mode on the result set (admin mode errors on refusal rather than returning a shorter list, member mode skips the admin sweep), and by noting that isAdmin and isMember can be null when the corresponding scope was not queried. These details go beyond the schema and are valuable for the agent.

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 slightly longer than ideal but every sentence contributes to understanding the tool's behavior. The opening sentence states the core function and return fields, followed by a clear breakdown of modes. The structure is logical and front-loaded, and while it is verbose, it avoids redundancy. A 4 is appropriate because it is efficient but not extremely terse.

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?

Despite having no output schema, the description lists the fields returned (id, displayName, sku, location, state) and the additional contextual flags (isAdmin, isMember). It fully explains the three modes and their implications, including error behavior for admin mode. The tool's complexity is well covered; an agent can call it correctly without additional information.

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 100%, with both parameters already described in the schema. The description adds meaningful semantic depth by elaborating on the mode parameter's behavior (e.g., default, performance implications, error handling) and the interpretation of the returned flags (isAdmin/isMember null when scope not queried). It also clarifies that 'top' controls pagination, though that is already in the schema; the description reinforces the default behavior for mode. This exceeds the baseline for 100% coverage.

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 states a clear, specific action ('List all Power Platform environments') and resource, and distinguishes itself from sibling tools by specifying 'directly from Power Automate' (i.e., live environments) as opposed to store-based tools like list_store_environments. It also enumerates the exact fields returned, making its scope 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?

The description gives concrete guidance on when to use each mode: mode=all is the default, mode=member is recommended for speed in large tenants (skips admin sweep), mode=admin requires admin credentials and errors on refusal. It does not explicitly compare to sibling list_store_environments, but the tool name and the 'live' vs 'store' distinction make the alternative obvious. The usage context is well specified for the modes.

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