save_all

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

No annotations are provided, so the description must disclose behavioral traits. It states a save operation, implying a mutation, but doesn't say whether it's a persistent disk write, what data is included, whether it's safe to call repeatedly, or what the output contains. The single sentence leaves almost all behavior opaque.

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 short sentence, which is appropriately concise. It's front-loaded with the action and object. However, the extreme brevity comes at the cost of usefulness, but on pure conciseness it's efficient with no filler.

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 that this is a zero-parameter tool with an output schema, the description should at least explain what 'world cache' encompasses and the effect of saving it. It doesn't. There's no indication of when to call it relative to other cache tools. The output schema exists, so return values are covered, but the operation's scope and side effects are not.

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 tool takes zero parameters, so there are no parameter semantics to describe. Per the rubric, zero parameters gets a baseline of 4. The description doesn't need to explain arguments, and none are missing.

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 'Save Baritone's world cache' is essentially a restatement of the tool name save_all combined with a vague notion of 'world cache'. It does not clarify what specifically is saved (location data? chunk cache? build state?) or distinguish this from sibling reload_all or clear_cache. Without more detail, it's nearly tautological.

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 whatsoever on when to use this tool. The description does not explain when to call save_all versus reload_all or other cache-related siblings like get_cached_block or cache_block. An agent would have no basis for selecting this tool over others.

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