azure_enumerate_role_definitions

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

With no annotations, the description must disclose behavioral traits. It states it 'checks' role definitions and identifies security issues, implying a read-only operation, but does not explicitly declare read-only nature, permission requirements, or potential side effects. The security focus is clear, but transparency about operation type is lacking.

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 concise with three sentences, front-loading the primary purpose and then adding specific security details. Every sentence adds value, and there is no redundancy or unnecessary fluff.

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 no output schema, the description covers the key purpose and security features. However, it does not explain the return structure (e.g., list of definitions) or the impact of the 'format' parameter. It is complete enough for an agent to understand the tool's value, but missing output details limits completeness.

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 baseline is 3. The description adds context about 'custom roles' which relates to the includeBuiltIn parameter, but does not provide additional semantics beyond what the schema already describes. No enrichment of parameter meaning.

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 specifies the tool's purpose: enumerating Azure RBAC role definitions, including custom roles. It further distinguishes itself by highlighting security-focused capabilities such as identifying wildcard permissions and privilege escalation paths, which sets it apart from sibling tools like azure_enumerate_rbac_assignments.

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 role definitions but lacks explicit guidance on when to use this tool versus alternatives (e.g., azure_analyze_rbac_privesc). No when-not-to-use or exclusion criteria are provided, leaving the agent to infer context from the name and sibling list.

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