List environments

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the backing API (BAP) and that results include Dataverse URLs, but says nothing about permission scope failures, pagination, throttling, or what happens when the user has no accessible environments.

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; scope and return content are stated up front. The '(BAP API)' parenthetical is mildly cryptic but earns its place as source attribution.

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 simple two-optional-param read tool with no output schema, the description covers what is returned at a high level (environments plus Dataverse URLs) and who it applies to. It omits authentication/permission prerequisites and result volume, which an agent would reasonably want before calling it in a multi-environment workflow.

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 description coverage is 100%, so both optional parameters (clientId, tenantId) and their fallback defaults are already fully documented in the schema. The description adds no parameter-level meaning, so baseline 3 applies.

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+resource ('List Power Platform environments') with a clear scope qualifier ('the signed-in user can access'), which separates it from the admin-scoped sibling cs_admin_list_environments. It does not explicitly name any sibling, so the differentiation is inferential rather than stated.

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?

There is no when-to-use, when-not-to-use, or alternative routing. Siblings such as cs_admin_list_environments, cs_env_list, and cs_env_select also deal with environments, and the description gives no rule for choosing among them.

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