list_methods

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

The description discloses that the tool is deprecated and an alias, which is important behavioral context. However, no annotations are provided, and the description does not explicitly state that it is read-only or safe, though the name 'read_cluster_memory' suggests so.

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 sentence that concisely communicates the tool's nature as a deprecated alias, with no unnecessary words.

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 deprecated alias tool, the description adequately conveys its role and relationship to another tool. The presence of an output schema compensates for missing return value details, but the description could briefly mention that the output is identical to read_cluster_memory.

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 input schema has 0% description coverage, and the description does not explain the 'cluster' parameter or how it is used. It only indirectly implies it is passed to read_cluster_memory, lacking direct semantic enhancement.

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 explicitly states it is a deprecated alias for read_cluster_memory(kind='methods'), making the tool's purpose clear and distinct from siblings like read_cluster_memory.

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 tells the agent that this tool is deprecated and an alias, implying it should use read_cluster_memory(kind='methods') instead, providing clear guidance on when not to use it.

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