azure_enumerate_service_principals

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

Annotations are empty, so the description must convey behavior. It mentions 'enumerate' suggesting read-only, and includes a permission requirement for credential validation in parameter descriptions. However, it does not explicitly state that the tool is read-only, nor does it disclose rate limits or API impact. The description is adequate but not thorough.

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 relatively concise, using bullet-style lists for features. It includes a version tag 'ENHANCED v1.14.0' which is unnecessary but not harmful. Each sentence contributes information, though the 'NEW:' prefix is somewhat redundant.

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 tool has 5 parameters and no output schema, the description gives a good overview of analysis areas and new features. However, it lacks detail on the structure of returned security findings (e.g., fields, risk prioritization format), which is necessary for effective use. Support for the output format parameter (markdown/json) is not explained.

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% with detailed parameter descriptions, giving baseline 3. The description adds context by linking parameters to features like credential hygiene (validateSecrets, expiryWarningDays) and privilege analysis (includePrivilegeAnalysis), enhancing understanding beyond 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 enumerates service principals with RBAC role assignments for security analysis. It lists specific analysis areas (privilege escalation, multi-subscription access, etc.), distinguishing it from sibling tools like azure_enumerate_rbac_assignments that focus only on role assignments without service principal context.

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 implies usage for security auditing of service principals but provides no explicit guidance on when to use this tool versus alternatives like azure_enumerate_managed_identities or azure_analyze_rbac_privesc. No exclusions or when-not-to-use information is given.

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