bridge_save_as

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the source disk file is left unchanged and that UUIDs are verified after reopen, but it omits permission/auth requirements, what 'protected' entails, and what happens on failure or UUID mismatch.

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 dense sentence that front-loads the operation and its two key constraints with no filler. It is arguably too compressed given the jargon ('protected destination', 'UUIDs checked after reopen'), but nothing is wasted.

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?

With no annotations, no output schema, and 0% parameter coverage, the description should compensate for far more than it does. It documents side-effect safety on the source but leaves parameter meaning, return behavior, and failure modes unspecified.

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% and neither 'project' nor 'output' is explained in the description or schema. The agent cannot tell whether 'project' is a name, ID, or path, or whether 'output' is a directory, filename, or format specifier.

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 (Native SaveAs) and resource (project file), plus the scope constraint that the destination must be NEW and protected. It does not name or contrast with plausible siblings like bridge_copy_project or bridge_preview_on_copy, so the agent gets a clear operation but no differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only inferred constraint is that the destination must be a new protected location, which is embedded in the purpose statement rather than framed as selection criteria.

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