list_entitlements

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds that results are paginated and that an invalid pool id produces a teaching 404. That is genuine behavioral context beyond the annotations, though it says nothing about result volume or rate limits.

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?

Three tight sentences with the [READ] tag and the core purpose front-loaded, then pagination and error/routing notes. Every sentence earns its place with no filler.

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 4-parameter read tool with no output schema, the description covers the essential call mechanics: what it returns (AD users/groups with access), pagination, and how to source the required pool id. It does not describe the shape of returned entitlement entries, but that is a minor omission given the absence of an output schema.

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 limit, offset, target and pool_id are all documented in the schema itself. The description adds only that pool_id comes from list_desktop_pools, which is useful but marginal; baseline 3 is appropriate.

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 verb (List) and resource (AD users/groups entitled to a desktop pool), with the clarifying gloss 'who can access it'. This cleanly separates it from siblings add_entitlement/remove_entitlement and from pool-listing tools.

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?

Explicitly routes the agent to list_desktop_pools for obtaining pool ids, and warns that a wrong pool id yields a teaching 404, which is actionable guidance. It lacks an explicit 'when not to use' or a note on when add/remove_entitlement would be the right call instead, so it stops short of a 5.

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