get_user_effective_azure_access

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

The annotations already declare readOnlyHint and idempotentHint, so the description adds value by detailing that access is computed as direct plus transitive group inheritance. This provides behavioral insight beyond the annotations without contradicting them.

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 a single clear sentence with no unnecessary words. It efficiently conveys the core purpose and scope, making it well-structured and concise.

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 is sufficient for an agent to understand what the tool does and when to call it, especially given its read-only nature and explicit inclusion of transitive groups. It does not describe output format, but there is no output schema, so this is not a major gap.

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?

The schema provides zero descriptions for parameters, and the description only implicitly covers 'user_identifier' via 'de um usuário'. The 'limit' parameter is not explained at all. Since coverage is 0% and the description does not compensate for the missing parameter semantics, the score is low.

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 that it resolves effective Azure RBAC access for a user, explicitly including both direct and transitive group inheritance. This is a specific verb ('resolve') and resource ('Azure RBAC access') that distinguishes it from sibling tools like list_azure_role_assignments or list_users_with_direct_permissions.

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 when to use it (for effective access including transitive inheritance) but does not explicitly mention alternatives or exclusion criteria. An agent can infer its use from the phrase 'direto + herdado via grupos transitive', but there is no direct guidance on choosing this over other list tools.

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