save_presentation

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

No annotations are supplied, so the description carries the full behavioral burden, and it only establishes that this is a write that targets the existing path. It does not disclose what happens for an untitled/never-saved presentation, whether prior file contents are overwritten or backed up, whether an open document is required, or what the call reports on success or failure.

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 verb first and zero filler. Nothing is repeated from the title and no sentence fails to earn its place.

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 zero-parameter, no-output-schema mutation tool, the description is adequate for identification but thin on operational context. The important edge case in this sibling set — an unsaved presentation with no current path — is left entirely unaddressed, and there is no hint of failure behavior.

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 tool takes zero parameters, so the schema leaves nothing to clarify and the baseline applies. The description adds no parameter meaning because there is none to add; it also does not explain that the save target is derived from implicit session state rather than any argument.

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 states a specific verb and resource ('Save the current presentation') plus a scope qualifier ('to its current path'), which implicitly separates it from the sibling save_as. It stops short of naming save_as directly, so the distinction relies on the agent inferring that 'current path' means no new destination.

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?

Usage is implied rather than stated: the phrase 'to its current path' suggests an in-place save rather than a save-as-new-file, which is the relevant fork against the save_as sibling. It never explicitly says when to prefer save_as, nor does it state the prerequisite that a presentation must already be open and have a path.

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