Save project

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is signaled structurally. The description adds the default-save-target behavior, but it does not explain overwrite semantics or what happens to an existing file when saving without a path, which is central for a destructive write.

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 tight sentences with zero filler, and the default-behavior rule is front-loaded before the exception about never-saved tabs.

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 destructive save tool with no output schema and one undocumented parameter, the description covers the common path but leaves overwrite behavior and the return/result unaddressed. Adequate but with a real gap given destructiveHint=true.

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 coverage is only 33%; only tabId is documented in the schema. The description compensates for 'path' by explaining absolute-path requirement and default resolution, but 'overwrite' is left completely unexplained in both schema and description.

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?

States a specific verb and resource ('Save the tab as a .snipaya project'), which is clearly distinguishable from the export siblings. It stops short of explicitly contrasting with snipaya_export/snipaya_export_to, but the concept is unambiguous.

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 gives useful default behavior ('Without path, saves to the tab's existing file; a tab that was never saved needs an absolute path'), which implies when a path is required. However, it never says when to choose this over export/export_to, nor any exclusions.

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