redis_slowlog

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

Beyond readOnlyHint=true, the description discloses a hard cap (128 entries), the ordering (slowest first), and the envelope shape with a 'truncated' flag and an explicit warning not to treat the result as complete. That truncation warning is a meaningful behavioral disclosure the annotations do not cover; only auth/permission context and pagination mechanics are absent.

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?

Front-loads the one-line purpose, then structured Args and Returns sections with no filler. The return-envelope paragraph is longer than strictly needed but earns its place because there is no output schema; the caveat sentence is the most valuable line in the definition.

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 0% schema coverage and no output schema, the description fully compensates by documenting both parameters and the return envelope including the truncation flag. What is missing is routing guidance relative to the many sibling RCA/diagnostic tools, which is the only real gap for an agent deciding whether to call it.

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 0%, so the description must carry the load, and it does: 'count' is explained as max entries with a 128 cap, and 'target' as a config target name whose omission selects the default. Both parameters gain meaning not present in the bare schema, though defaults are not restated.

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 and resource ('Recent SLOWLOG entries') plus an ordering guarantee ('slowest first'), and the [READ] prefix signals the operation class. An agent can distinguish this from redis_latency_rca, redis_server_info, and the other redis diagnostics without opening the 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?

The description never says when to reach for this tool versus siblings like redis_latency_rca or redis_memory_pressure_rca, nor any preconditions. Only implicit context ('slowlog') suggests a latency-diagnosis scenario. No exclusions or alternative routing are provided.

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