get_slot_stats

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

No annotations provided, so description carries full burden. It discloses version dependency and error behavior, but doesn't mention read-only nature, permissions, or rate limits. Reasonable but not comprehensive.

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 sentences, front-loaded with core purpose and version requirement. Second sentence adds actionable guidance and error note. No wasted words.

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?

Missing output schema and description doesn't specify return format (e.g., list of slots with keys and CPU usage). Adequate for usage but lacks full picture of response structure.

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 has 100% description coverage, so baseline is 3. Description adds value by explaining real-world use cases for orderBy (finding hot vs populated slots) and emphasizing default for limit, enhancing beyond schema alone.

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 clearly states 'Get per-slot key counts and CPU usage' and notes 'Valkey 8.0+ only', providing specific verb and resource. Distinguishes from sibling tools like get_hot_keys and get_largest_keys by focusing on slot-level statistics.

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 suggests using orderBy='cpu-usec' for hot slots and 'key-count' for populated slots, giving clear usage context. Mentions error handling for unsupported versions but doesn't compare directly with sibling tools.

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