Redis GET

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

Description says 'GET' implying a read-only operation, but annotations set readOnlyHint to false, creating a direct contradiction. No other behavioral details (errors, side effects) are disclosed, and annotations don't cover the safety profile.

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, clear sentence that front-loads the verb and resource. It is appropriately concise for a simple tool, though it could include a bit more without becoming verbose.

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 description omits important behavioral context, especially given the annotation contradiction. It doesn't mention error behavior, connection requirements beyond url, or the return value (though an output schema exists). For a tool with no helpful annotations, this is insufficient.

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?

The description explains the 'url' parameter's purpose as a connection URL, which is beyond the schema (0% coverage). However, 'key' is not described at all, and the schema provides no context. It partially compensates but leaves the key parameter underspecified.

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 states 'GET a redis key' – a specific verb and resource. It's clear and unambiguous. It doesn't explicitly differentiate from siblings because no other redis tool exists, but it does convey the exact operation.

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?

It provides a precondition: 'needs REDIS_URL or url=' – useful for invoking the tool correctly. However, it doesn't discuss when to use this tool vs alternatives (none exist) or when not to use it, so guidance is limited to a prerequisite.

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