Save Project

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

The annotation already indicates idempotency. The description does not add behavioral context beyond this, such as overwriting behavior, default save location, or side effects. Since the annotation carries the main burden, the description's contribution is minimal.

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 extremely concise (8 words) and front-loaded with the core purpose. Every word is necessary, but it could be expanded slightly 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?

For a save operation, the description omits critical context: what file is overwritten, whether a backup is created, and the effect of omitting the path. With many sibling tools and no output schema, the description should provide more complete context.

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 explains that 'path' is for specifying a new save location, which adds meaning beyond the schema (which only shows type and default). However, it fails to clarify what happens when path is not provided (e.g., saves to current project location) and lacks format details.

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 matches the name and title. However, it does not differentiate from sibling tools like 'load_project' or 'save_style_qml'.

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 description lacks guidance on when to use this tool versus alternatives. No exclusions or context for choosing 'save_project' over similar tools like 'save_style_qml'.

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