Save Project

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

The description adds 'Save the current project' which implies a write operation, but annotations already provide idempotentHint=true. No additional behavioral details (e.g., overwrite behavior, notification) are provided.

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?

Two sentences, front-loaded with purpose, no wasted words. Perfectly concise.

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?

Adequate for a simple save operation with one optional parameter and idempotency annotation. Missing details on default behavior when path is null or any return value.

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 description clarifies the 'path' parameter as an optional new save location. This adds meaning to the schema, but could be more precise about path format or defaults.

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 states the tool saves the current project, which distinguishes it from sibling tools like create_new_project and load_project. However, it does not elaborate on what 'save' entails (e.g., overwriting original).

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 tool versus alternatives. It only mentions optional path, but does not contrast with create_new_project or load_project.

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