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

'Read-only despite being a POST' is a genuinely useful disclosure that reinforces and explains the readOnlyHint=true annotation, warning the agent off assuming a mutation from the HTTP verb alone. It does not, however, mention pagination/limit behavior, which the schema carries instead.

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 filler; the purpose and the read-only caveat are both front-loaded before the trailing API path reference.

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 three-parameter read-only list endpoint with full schema coverage, the description plus annotations cover what an agent needs to invoke it. With no output schema, a brief note on the returned shape would have closed the remaining gap.

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, cursor, and namespace are each documented in the schema already. The description adds no format or constraint detail beyond that, so the baseline 3 applies.

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?

Specific verb ('List') plus resource ('per-identifier overrides') and scope ('in one rate-limit namespace'), which implicitly separates it from the singular unkey_get_ratelimit_override sibling. It never explicitly names the sibling or states the list-vs-single distinction, so it falls short of the 5 bar.

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 on when to choose this over unkey_get_ratelimit_override or unkey_set_ratelimit_override, nor any prerequisite or pagination-flow advice. Usage is left entirely to inference from the name.

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