list_pool_entitlements

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered there. The description adds useful return-shape context ("which users and groups are entitled to each pool"), but says nothing about pagination, result size, or how entitlements are ordered. Given the annotations carry the safety burden, a 3 is appropriate.

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 with zero waste: the primary scope statement is front-loaded, followed by the return contents and the sibling pointer. Nothing needs to be re-read or clipped.

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?

With an output schema present, the description needn't detail return format, and annotations cover the safety profile; the one required param is fully documented in the schema. What remains missing is minor guidance such as result size or whether entitlements can be filtered by user or group, but nothing essential to a correct call is absent.

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% and the single pool_type parameter already carries an enum and description. The phrase "of the given type" in the description maps directly onto that enum but adds no syntax or semantics beyond it. Baseline 3 is correct when the schema does the heavy lifting.

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 (entitlements for pools of a given type), and explicitly scopes it to all pools rather than one. It names the sibling get_pool_entitlement as the single-pool alternative, so an agent can distinguish the two without opening either schema.

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 get_pool_entitlement for a specific pool's details, giving a clear use case for the alternative. It does not, however, mention set_pool_entitlements as the mutation counterpart, so the read-only vs. write boundary is left implicit.

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