Run any pac command

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

No annotations are provided, so the description carries the full burden, and it does disclose a real behavioral trait: read-only commands (list/who/status/help) run immediately while anything else requires confirm: true. The list of exempt commands adds information the schema does not contain. It omits the potential destructiveness of arbitrary pac subcommands and output format, so it is not exhaustive.

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?

Three tight sentences, front-loaded with the escape-hatch framing, then the safety gate, then the profile note. Every clause carries information; there is no filler or repetition of the title.

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 generic 5-parameter escape hatch with no output schema and no annotations, the description covers the safety gate and profile semantics but says nothing about return shape, error behavior, or when to avoid this tool in favor of a dedicated sibling. Adequate but with clear gaps.

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?

With 60% schema coverage, the description usefully supplements the schema: it clarifies which commands trigger the confirm gate and explains that 'profile' runs the command as another pac auth profile, with a concrete example (tenant admin account). It adds nothing for cwd or timeoutSeconds, but those are self-descriptive.

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 specific verb and resource — run 'pac <args...>' directly — and labels itself an 'escape hatch', which clearly differentiates it from the many dedicated cs_* wrappers. It stops short of naming those siblings or saying to prefer them, so the differentiation is implicit rather than explicit.

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 'escape hatch' framing implies this is a fallback when no dedicated tool exists, and the read-only vs. confirm split gives some when-to-use context. However, with 90+ siblings covering the same pac surface, the description never tells the agent to prefer cs_env_list, cs_login, etc. over this generic tool, leaving the routing decision to inference.

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