redis_health

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

Annotations already declare readOnlyHint and idempotentHint. The description adds extensive behavioral detail about the specific metrics and data sources (INFO, DBSIZE, SLOWLOG), which goes beyond annotations and provides transparency about what the tool accesses.

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?

The description is a single well-structured paragraph that front-loads the key metrics. It is concise given the amount of information, though it could be slightly more scannable with lists.

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?

Despite no output schema, the description thoroughly explains what will be returned. The single parameter is fully documented in schema. The tool is simple and the description covers all necessary context for selection and invocation.

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 coverage is 100%, so baseline is 3. The description mentions slow commands in context but does not add new meaning to the 'slowlogLimit' parameter beyond the schema's description. No additional value provided.

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?

The description clearly states the tool provides a health snapshot from INFO, DBSIZE, and SLOWLOG, listing specific metrics like server version, memory, clients, ops/sec, keyspace, persistence, replication, and recent slow commands. It distinguishes itself from siblings like redis_slowlog by being a rolled-up summary.

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 explicitly says 'Use as a connection sanity check and the first stop in 'why is Redis slow / using so much memory?' triage,' providing clear when-to-use guidance. It does not explicitly exclude alternatives like redis_advisor, but the context is sufficient.

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