List service principals with Dataverse access

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully states that it runs 'pac admin list-service-principal' and uses the active pac auth profile, covering the auth dependency. However, it does not explicitly state that it is read-only or describe any side-effect absence or output behavior.

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?

The description is two short sentences. It front-loads the core purpose and immediately gives the exact execution command, with no filler or redundant 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?

Given the fully documented parameter schema and the simplicity of a list operation, the description provides enough context to select and invoke the tool. It would be stronger with explicit output-shape or side-effect disclosure, but nothing essential for calling the tool is missing.

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 coverage is 100%, so the baseline is 3. The description adds a bit of command context by naming the exact pac command, but it does not enrich the semantics of max, filter, cwd, or timeout beyond what the schema already provides.

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 definition clearly identifies the action ('List') and the specific resource: service principals with Dataverse access, described as Entra applications with an application user in Dataverse. It names the underlying command, making it distinct from sibling list tools like cs_admin_list_applications.

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?

It gives clear context for when this tool is appropriate: finding application identities that can act without a person signing in. It does not explicitly name alternatives or provide when-not conditions, but the purpose is specific enough to guide selection.

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