project_save

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Save the project' implies a write operation, but it does not state whether the current file is overwritten, whether unsaved changes are persisted, or what happens if no project file is currently open.

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 three-word sentence with no filler, making it extremely scannable and front-loaded. It is concise in form, though the brevity also limits the behavioral context it provides.

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 low complexity (no parameters, no output schema, no annotations), naming the action may be minimally adequate. Still, the description omits crucial contextual details such as whether the save overwrites the existing file, requires a previously opened project, or produces any confirmation or error response.

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 input schema has zero parameters, so there is no parameter detail the description must compensate for. The baseline of 4 applies because no parameter semantics are needed.

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 clearly identifies the action ('save') and the target resource ('the project'). However, it does not distinguish this from sibling tools like project_save_as or project_save_undo, so the agent must infer the exact scope from the name alone.

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 given for when to use this tool versus alternatives such as project_save_as, project_save_undo, or project_new. The agent is given no context about when this command is appropriate or what distinguishes it from related project commands.

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