get_indexes

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

The description states the return type (JSON string of indexes or error), but with no annotations, it misses details like read-only nature or side effects. It adds some value beyond the schema by describing the output.

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?

Two sentences with no wasted words: the purpose is front-loaded ('List of indexes in the Redis database'), and the return type is clearly stated.

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 parameterless tool with an output schema, the description provides adequate context: what it does, what it returns. Could mention that it lists all indexes, but overall complete.

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?

With 0 parameters and 100% schema description coverage, baseline is 3. The description does not add parameter info as none exist, but it explains the return value which is part of the output schema.

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 'List' and resource 'indexes in the Redis database', clearly distinguishing from siblings like get_index_info (specific index) and get_indexed_keys_number (count).

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 explicit guidance on when to use this tool vs alternatives. Siblings like get_index_info and get_indexed_keys_number exist, but the description does not mention them or specify scenarios.

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