rew_save_all_plan

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

No annotations are provided, so the description carries the full burden. It discloses only the core action, not what 'hash-bound' means, potential side effects, prerequisites (e.g., live REW measurements), or whether it is read-only. Transparency is minimal.

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?

A single, front-loaded sentence that efficiently communicates the core purpose. While it lacks detail, the structure is clean and free of fluff, earning a high score on conciseness even though it is under-specified.

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?

With no annotations, no output schema, and 0% parameter descriptions, this tool demands far more context. It omits critical details: what a 'plan' entails, how to proceed after creation, and descriptions of 'home' and 'note'. An agent would have to rely on convention or other means to use it correctly.

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?

Schema description coverage is 0%, so the description must compensate. It does not explain any of the three parameters (home, note, saveFile). Only 'saveFile' is inferred via 'MDAT'; 'home' and 'note' are completely unexplained, leaving the agent without essential parameter meaning.

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?

States a specific verb ('Create'), a specific resource ('hash-bound plan to save all live REW measurements'), and a specific output ('new workspace MDAT'). It clearly distinguishes itself from execution siblings like 'rew_save_all_execute' by focusing on the planning phase.

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?

Provides no guidance on when to use this tool versus alternatives. It does not mention a corresponding execute tool, prerequisites, or when not to use it. The '_plan' suffix implies a workflow but is not explicit.

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