cmw_recall_state

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

The description adds minimal extra context beyond the annotation (destructiveHint: true). It does not elaborate on what gets destroyed or how state is overwritten, which is important for a destructive operation.

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?

Single sentence with a clear prefix, but it could include more detail without becoming verbose. It is appropriately front-loaded.

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?

Given the destructive annotation and two optional parameters, the description is incomplete. It does not explain what the alias or params_json are, nor what the output schema provides.

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 provides no explanation of the two parameters (alias, params_json). With 0% schema coverage, the tool relies entirely on the description for parameter meaning, which is absent.

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 clearly states it loads instrument state from a file, using a specific verb and resource. It distinguishes itself from sibling tools like mxa_recall_state or save_state.

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 or when not to use this tool. The context implies it is for recalling a previously saved state, but no alternatives or exclusions are mentioned.

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