save_structure

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

With no annotations, the description carries the full disclosure burden. It does reveal the serialization format (gzipped .nbt) and default destination, but says nothing about overwrite behavior, whether it requires an already-open structure, error conditions, or permissions — critical for a write/serialize tool.

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 with no waste. It is efficient, though arguably under-specified rather than concise — the parenthetical default is the only supporting detail.

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?

An output schema exists, so return values need not be explained. However, for a save operation with zero annotations and no parameter descriptions, the definition omits overwrite/error behavior, leaving the agent with gaps about side effects.

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 explains that name feeds the default path pattern (<workspace>/<name>.nbt) and implies path overrides it, which adds real meaning, but does not clarify path semantics such as absolute vs relative or whether directories are created.

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 and resource ('Save ... structure') plus the output artifact format (.nbt, gzipped), which clearly distinguishes it from siblings like open_structure, new_structure, or list_structures. It stops short of explicitly naming those alternatives, but the action is unambiguous.

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 on when to use this versus open_structure or new_structure, no prerequisites, and no mention of what happens if the target already exists. The agent must infer the workflow entirely from the name.

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