apple_pages_save

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, but the description adds the specific destruction condition: which paths trigger overwrite and that the current document path counts as existing. The 'no implicit format conversion' note is also useful behavioral context. The stray 'TextEdit saves RTF' sentence adds confusion rather than transparency.

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 overwrite rule is front-loaded and the tool is described in three short sentences. However, the 'TextEdit saves RTF; no implicit format conversion' sentence appears to be template bleed from a sibling tool and does not earn its place in a Pages save description.

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 mutation with no output schema, the definition covers the overwrite guard, path constraints and format behavior, which is what an agent needs to call it safely. Return-value behavior is unspecified, but that is a minor gap given no output schema exists.

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 only 33% (only documentName documented), so the description must carry path and overwrite. It does: path must be a .pages path with an existing parent directory, and overwrite:true is required for any pre-existing path. That compensates well for the undocumented parameters, though no syntax examples are given.

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+resource+destination ('Save Pages to a .pages path'), which cleanly distinguishes it from apple_pages_export, apple_numbers_save and apple_keynote_save by naming the file type and target. It never names a sibling tool directly, so sibling differentiation is implied rather than explicit.

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?

Gives one concrete usage rule — existing paths (including the current document path) require overwrite:true — which is real when-to-use guidance for the overwrite parameter. It offers no guidance on when to save versus use apple_pages_export, and no prerequisites beyond the parent-directory requirement.

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