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

With no annotations, the description carries the full behavioral burden. It makes clear this is a non-mutating listing operation and discloses pagination by cursor, which is useful. However, it does not clarify ordering, page-size behavior, or whether an omitted prefix returns all keys.

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?

A single focused sentence with no filler. The key behavior and pagination mechanism are front-loaded, and every word contributes to understanding the tool.

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 tool with five parameters, no annotations, no output schema, and low schema coverage, the description is too sparse to make invocation fully reliable. It fails to clarify what slug refers to, how limit behaves, or what a paginated response looks like.

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 only 20%, so the description must compensate for undocumented parameters. It adds meaning for prefix and cursor, but the required slug parameter is left unexplained and limit semantics are absent, leaving the agent to infer too much.

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?

Description uses a specific verb ('List') and resource ('KV keys'), and distinguishes itself with two concrete behaviors: prefix filtering and cursor pagination. This clearly separates it from siblings such as kv_get, kv_put, and kv_delete.

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 for when to use the tool: listing KV keys under a prefix and paginating with a cursor. It stops short of explicitly naming alternatives or exclusions, so it is good but not fully directive.

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