Redis Info

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

With no annotations, the description carries the full burden, but it only lists content categories and does not disclose whether the command is read-only, whether all sections are returned at once, whether sections can be selected, or whether any authentication or Redis configuration is needed.

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 extremely short and wastes no words, front-loading the core content in a single phrase. However, it is a fragment rather than a complete sentence, and the brevity sacrifices explicit behavioral and parameter clarity.

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?

The output schema may cover return-value structure, and there are no required parameters, but the flexible params object is left entirely unexplained. An agent still does not know whether providing params is necessary, optional, or how to specify subsets of the named sections.

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%, and the only parameter is a free-form params object with no documented properties. The description mentions section names but never explains whether or how they map to the params object, leaving the agent to guess how to customize the call.

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 identifies the target resource (Redis INFO) and narrows it to specific sections: memory, clients, stats, replication. This gives an agent a concrete idea of what the tool exposes, though it lacks an explicit verb such as 'returns' or 'gets'.

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?

No guidance is given about when to use redis_info instead of sibling tools like redis_memory, redis_clients, or redis_slowlog. The section list implies broad diagnostic use, but there is no stated condition, scenario, or excluded alternative.

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