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

Beyond annotations, the description discloses important behavior: it snapshots the exact saved state and never publishes, and it explicitly does not accept a boolean claiming consent. This adds meaningful safety context beyond readOnlyHint=false, idempotentHint=true, and destructiveHint=false. It still does not describe operational details such as permissions, failure modes, or how the snapshot is returned.

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 description is two tight sentences with no filler, and the core purpose is front-loaded. The second sentence adds a high-value safety constraint rather than repeating structured fields. Every sentence earns 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?

This is a complex seven-parameter tool with a nested object and low schema description coverage. The description covers purpose and publication safety, but it leaves parameter meaning and operational context largely unexplained. An agent would still lack the information needed to understand how to populate or interpret most required inputs.

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 14%, and the description does not explain any of the seven parameters. It vaguely references 'saved draft' and 'destination revisions' but does not clarify draft_id, expected_revision, request_key, workspace_id, calendar_anchor, timezone, or native_schedule. With six required parameters and a nested object, the description fails to compensate for the schema's low documentation coverage.

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 uses a specific verb, 'Snapshot,' and names concrete resources: saved draft, assets, destination revisions, and visibility/disclosures. It makes clear this is a preparation step for creator approval and not publication. It does not, however, distinguish this from the closely related prepare_social_publication or schedule_social_draft siblings.

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 implies usage before authenticated creator approval and states 'Preparation never publishes,' which gives a useful boundary. But it does not explicitly say when to choose this tool over prepare_social_publication, schedule_social_draft, or publish_social_draft. The guidance is implied rather than explicit.

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