list_entra_users

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the output field detail, but it does not mention pagination, limit behavior, or whether all or only some users are returned.

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 one concise, front-loaded sentence with no filler. It states the action, target resource, and expected output fields efficiently.

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 simple list tool with strong read-only annotations, the description provides the essential output fields. However, it lacks mention of the limit parameter's effect and does not differentiate from the similarly named sibling 'list_users', leaving selection and pagination behavior partially underspecified.

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 only parameter, 'limit', is defined in the schema with a default of 20, but the description adds no meaning to it. With 0% schema description coverage, the description should compensate, but it omits any mention of pagination or how the limit affects results.

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 clear action ('Lista usuários') and resource ('Microsoft Entra ID'), and specifies the output fields (nome, UPN, e-mail). It is unambiguous about what the tool does, though it does not distinguish itself from the sibling 'list_users' tool.

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 about when to use this tool versus alternatives such as 'list_users', 'list_users_without_mfa', or other list-oriented tools. No context, prerequisites, or exclusions are provided.

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