list_users_with_direct_permissions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds one genuine behavioral nuance – that only DIRECT (not inherited) assignments count – but says nothing about pagination, result size, or required permissions.

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?

A single front-loaded sentence with no filler or repetition. It is well-structured, though its brevity contributes to the missing parameter and usage detail rather than being a flaw of the sentence itself.

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?

For a 2-parameter tool with 0% schema description coverage, no output schema, and dozens of closely related siblings, a one-line description is insufficient. It omits the filter semantics (disabled_only), result limiting, and any tie-breaker against neighboring list tools.

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 0% and both parameters (limit, disabled_only) are undocumented in the schema. The description never mentions either parameter, so it does not compensate for the coverage gap – an agent cannot tell that disabled_only filters to disabled accounts or how limit behaves from this text.

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 states a specific verb and resource ('Lista usuários com role assignments diretos no Azure RBAC'), and the 'diretos' qualifier meaningfully narrows it away from inherited assignments. It does not, however, explicitly name or differentiate itself from siblings like list_users, list_azure_role_assignments, or list_disabled_users_with_active_roles.

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?

There is no guidance on when to use this tool versus the many adjacent siblings (list_users, list_azure_role_assignments, list_privileged_azure_role_assignments, get_user_effective_azure_access). The agent must infer the distinction from the tool name alone.

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