inforcer_users_list

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context about pagination, tenant identifier resolution, and that only summaries are returned, but does not disclose page size, ordering, or search semantics. No contradiction with annotations.

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?

Four short sentences with the main purpose front-loaded and no filler. The tenant-resolution detail is relevant for correct invocation, and the read-only note is redundant but brief.

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 read-only listing tool with all parameters documented in the schema, the description covers the key invocation details: what is listed, pagination, and tenant identifier accepted forms. The lack of an output schema makes 'user summaries' slightly vague, but it is sufficient for an agent to select and call the tool correctly.

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 schema documents all three parameters. The description adds no new parameter meaning beyond restating the tenant formats and the 'paginated' behavior already visible in the 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?

States a specific action ('List'), precise resource ('Entra ID user summaries for a tenant'), and signals pagination. This clearly differentiates it from sibling inforcer_users_get, which is the single-user counterpart.

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 makes the scope of the tool clear, but does not explicitly advise when to use this tool versus inforcer_users_get or how search/pagination should be used. Usage context is implied by the verb 'List', but no exclusions or alternative routing are provided.

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