List Dynamics 365 app templates

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

There are no annotations, so the description carries the behavioral burden. It discloses that it runs 'pac admin list-app-templates' with the active pac auth profile, which is useful, but it does not explicitly state read-only behavior, output shape, or any side-effect-free guarantee beyond what 'list' implies.

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?

Two sentences, front-loaded with the core purpose and scoped by region, followed by the underlying command. There is no redundant or filler content.

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?

The description covers purpose, scope, and command, and the schema covers all parameters. However, with no annotations and no output schema, it does not describe the return format or explicitly confirm there are no side effects, leaving a moderate gap for an agent deciding how to use the result.

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 parameters are already fully documented. The description adds no parameter-specific meaning beyond 'per region' and the active auth profile, both of which are also reflected in the schema.

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 clearly states the tool lists Dynamics 365 application templates available per region, with a concrete underlying command. It names a distinct resource not covered by any sibling admin list tool, so an agent can differentiate it from cs_admin_list_environments, cs_admin_list_applications, etc.

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 clear context: these are templates used when creating an environment, and results are region-specific. It does not explicitly name alternative tools or state when not to use it, but the usage context is unambiguous.

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