save_project

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

With no annotations, the description carries full burden, but it only says 'Save the current project'. It doesn't disclose whether saving overwrites the existing file, if it creates a new file, or if it requires a path. Behavior like overwriting or prompting for confirmation is hidden. This is insufficient for a mutation 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?

The description is very short (one sentence) but is concise. However, it is under-specified for a tool with multiple sibling tools and no annotations. A slightly longer description with more detail would improve usefulness without losing conciseness.

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 tool's complexity (1 param, no annotations, no output schema) and the large number of sibling tools, the description is incomplete. It doesn't explain the return value, error conditions, or how it differs from similar tools like collect_files. The agent would likely struggle to use this tool 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?

There is only one optional parameter (path), and the schema description covers it fully. The tool description adds no extra meaning beyond the schema, so with 100% schema coverage, a baseline of 3 is appropriate. However, it could clarify what happens if path is omitted (e.g., save to current file).

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 tool name and description clearly state it saves a project, but the description 'Save the current project' is generic and doesn't distinguish it from sibling tools like close_project or open_project. The scope is vague (e.g., does it save to the current file or ask for a new one?). With 42 sibling tools including save-related ones, more specificity is needed.

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 is provided on when to use save_project versus alternatives like collect_files or reduce_project, which also involve saving. There's no mention of prerequisites (e.g., project must be open) or when not to use this tool. The context hints are not leveraged.

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