get_key_info

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

With no annotations provided, the description carries the full burden of disclosure. It does not reveal whether the operation is read-only, what fields of 'detailed information' are returned (e.g., type, TTL, encoding), or any permissions required. This is insufficient for a tool with no structured safety hints.

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 concise—a single sentence—and the key detail is front-loaded. However, it is under-specification rather than efficient conciseness, earning a 4 instead of a 5 because it omits necessary qualifiers.

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?

For a simple tool with one parameter and no output schema, the description should clarify what 'detailed information' means and how it differs from get_data. Given the large sibling set and no annotations, the description is incomplete for reliable 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?

The schema covers the only parameter 'key' with a description ('Redis key to get info for'), achieving 100% coverage. The tool description adds no further semantic detail, so the baseline score of 3 applies; the schema already documents what the parameter is.

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 uses a specific verb ('get') and a resource ('key'), but 'detailed information' is vague and does not distinguish this tool from siblings like get_data (which likely retrieves values) or get_redis_info (which retrieves server info). It states what it does but not what 'information' entails.

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 provided on when to use this tool versus alternatives. The sibling tools (get_data, exists_key, list_keys) indicate related but distinct operations, yet the description offers no exclusions or comparisons to help an agent choose correctly.

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