entitlement_list

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral details beyond those annotations: pagination and the teaching 404 on a wrong pool id, which helps the agent handle failures gracefully. No contradiction exists.

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?

Two short sentences carry all essential information: purpose, pagination, error behavior, and id-sourcing guidance. The most important scoping information is front-loaded, and no filler or repetition is present.

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 read-only paginated list tool with robust annotations and fully documented parameters, the description is complete. It covers what the tool returns (entitled AD users/groups), how pagination works, the failure mode on invalid ids, and where to get valid ids. No additional context is needed for correct invocation.

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 already documents all four parameters, including the default limit/offset and the target field. The description adds only minor value by connecting pool_id to pool_list, but this is already echoed in the schema; thus 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?

The description states a specific verb ('List'), a concrete resource ('AD users/groups entitled to a desktop pool'), and an accessibility gloss ('who can access it'). The term 'List' plus the entitlement_set naming distinguishes it from sibling tools like entitlement_add and entitlement_remove, and the reference to pool_list differentiates it from that sibling.

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 gives clear context: it is paginated and requires a pool id, and it explicitly routes users to pool_list for obtaining valid ids. It does not explicitly state when not to use the tool or name alternatives for modifying entitlements, but the context is strong enough for an agent to use it correctly.

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