save_project

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

No annotations are supplied, so the description carries the full burden. It does disclose the critical destructive behavior — omitting path overwrites the existing file — which is genuinely useful. It says nothing about permissions, error behavior for invalid paths, or what the tool returns on success, leaving meaningful gaps for a write 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?

The English sentence is front-loaded and efficient, but the entire content is duplicated verbatim in Japanese, adding length without adding information for an agent reading the English. Nothing is wasted conceptually, but the payload is roughly twice the necessary size.

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 one-parameter save tool with no output schema and no annotations, the description covers the essential mode switch but omits what happens on failure, whether the .ustx extension is enforced, and what confirmation is returned. Adequate but not fully complete.

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 coverage is 0% and the single parameter 'path' has no schema description, so the description must compensate. It does: it tells the agent path is a destination file for .ustx output and that null/omitted means save in place, which covers both meaningful states of the parameter.

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 the project) plus the concrete output format (.ustx), which implicitly separates it from export_midi/export_wav siblings that produce other formats. It never names an alternative explicitly, so sibling differentiation is inferred from the format rather than stated.

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 path-omitted case is spelled out ('overwrites the current file'), which tells the agent how to invoke it in two modes. There is no guidance on when to prefer this over export tools or what preconditions must hold (e.g., a project being open).

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