Self-elevate to System Administrator

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

With no annotations, the description carries the full burden and discloses the key traits: it mutates a live environment, requires explicit confirmation, returns a dry run without it, needs caller admin rights, and runs via the active pac auth profile. It stops short of stating irreversibility or downstream effects, but the mutation/confirmation/auth profile is well disclosed.

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?

Mostly front-loaded and understandable, but it redundantly states the mutation/confirmation rule twice ('Changes a live environment: requires confirm: true' and again 'Mutates a live environment: requires confirm: true (a dry run otherwise)'). That duplication wastes space in an otherwise short description.

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 privileged mutation with no annotations and no output schema, it covers the essentials: prerequisite admin role, confirm requirement, dry-run fallback, underlying command, and auth-profile behavior. Missing only return-value and reversibility context, which is minor here.

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 the schema already documents cwd, confirm, profile, background, environment, and timeoutSeconds. The description reinforces the confirm semantics (dry run without it) but adds no format or value guidance beyond the schema, so the baseline 3 is appropriate.

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 action (grant yourself the System Administrator role) on a specific resource in an environment, and names the underlying operation ('pac admin self-elevate'). It is clearly distinguishable from sibling cs_admin_* list/set tools, which deal with environments, settings, and policies rather than granting the caller admin.

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?

Gives a concrete prerequisite ('Needs Global, Power Platform or Dynamics 365 admin') and the gating condition for actually performing the change ('requires confirm: true', dry run otherwise). This is clear context for when it will and won't act, though it does not name alternate tools for elevation or post-elevation workflows.

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