Reassign an agent's owner in its environment

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

With no annotations, the description carries the full burden and does so well: it flags that it mutates a live environment, that confirm: true is required or the call is a dry run, that it runs the pac command under the active auth profile, and that it is an admin operation implying elevated credentials.

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?

Four tight sentences, front-loaded with the action and effect, then the sibling disambiguation, the underlying command, and the mutation/dry-run constraint. No filler; each sentence adds decision-relevant information.

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 an 8-parameter admin mutation with no annotations and no output schema, the description covers the safety-critical traits (live mutation, dry-run default, auth profile, alternative tool). It omits what happens to the previous owner and any downstream effects, a minor gap rather than a blocking one.

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 botId, newOwner, profile, confirm, environment, background etc. are already documented. The description only reinforces the confirm dry-run behavior already present in the schema, adding little parameter syntax or format detail beyond that; 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 verb and resource: transfer ownership of a Copilot Studio agent so the new owner can edit/publish/manage it. It also explicitly distinguishes itself from cs_reassign_org_agent, which handles the Microsoft 365 side, so an agent can pick the right tool without opening schemas.

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?

Clear context is given: this is an admin operation scoped to the Power Platform environment, and the sibling cs_reassign_org_agent covers the M365 side. However, it stops short of stating explicit when-not conditions (e.g. tenants without admin rights) so it does not reach a full 5.

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