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

Goes well beyond the annotations by disclosing that stale revisions are rejected (optimistic concurrency), that image IDs from another profile are refused (cross-profile scoping guard), and that manual edits incur no cost. These are exactly the kind of failure modes and side-effect boundaries an agent cannot derive from destructiveHint/idempotentHint alone.

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?

Four short sentences, front-loaded with the core action and constraint, and each clause carries distinct information (revision guard, profile guard, cost, non-effects). No filler or repetition, though the phrasing is clipped into fragments rather than a flowing structure.

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, non-idempotent mutation with no output schema, the description covers side-effect boundaries, rejection conditions, and cost, which is most of what an agent needs. It leaves permission/auth requirements and the shape of the document payload unaddressed, but the essential behavioral picture is complete.

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% across all three required parameters, so the description must carry the burden. It only hints at 'revision' semantics (staleness) and image IDs inside the document; projectId and the free-form document object remain entirely unexplained despite nested-object complexity.

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 (save an edited Studio document) and pins the scope to its current revision. The closing clause ('No publishing or AI generation occurs') actively differentiates it from siblings like create_post and studio_generate, so an agent can route correctly without opening a schema.

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?

It implies the correct context by ruling out publishing and AI generation, and notes that stale revisions are refused, but it never states an explicit when-to-use condition or names an alternative sibling (e.g., use studio_generate to produce content first). Usage is inferable rather than stated.

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