save_project

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

With no annotations, the description does carry real weight: 'overwrite' signals a destructive write and 'after explicit confirmation' flags a confirmation gate, plus a post-write verification step. It stops short of disclosing what the incremental-vs-full behavior is, whether prior state is recoverable, or what happens if confirm is false.

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?

A single front-loaded sentence with the destructive verb first and no filler; nothing in it is wasted. It is arguably too terse for the amount of undocumented behavior, but as structure it is clean.

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?

A destructive, no-annotation tool with 0% schema coverage and two opaque parameters. An output schema exists so return values needn't be described, but the description leaves the mode semantics, the confirmation contract, and failure behavior unstated — gaps an agent would have to guess at.

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 description coverage is 0%, so the description must explain the two parameters and largely doesn't. 'explicit confirmation' gestures at the confirm boolean but never says it must be true to proceed, and 'mode' (default 'Incremental') is entirely unexplained — the agent cannot tell what alternate modes exist or what they change.

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?

Specific verb pair ('overwrite and verify') against a specific resource ('the current saved project'), so an agent knows this persists the open project state rather than creating a copy. It does not explicitly distinguish itself from the sibling save_project_copy, which is the main residual ambiguity.

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?

'after explicit confirmation' implies a precondition for calling, but the description never states when to prefer this over save_project_copy or what the trigger conditions are. Usage is inferable rather than spelled out, and no exclusions are given.

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