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

The annotations already declare that this is a non-destructive but non-read-only open-world operation, and the description adds substantial context beyond that: it reads the current content, detects or uses the target query, runs live research, compares the content, saves a brief to the Library, and returns both a refresh brief and a revised draft. It also gives the expected runtime of three to six minutes and explains how the returned artifacts should be handled.

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 long but front-loads the core purpose and is organized around what the tool reads, compares, returns, and requires. Most sentences earn their place by conveying process or input requirements, though some explanatory detail could be tightened.

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 complex multi-step tool with no output schema, the description is complete: it explains the workflow, required inputs, source precedence, expected runtime, and the two returned artifacts. An agent has enough information to decide whether to call it and how to present the results.

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 coverage is 100%, so the schema already documents all eight parameters, and the description does not need to redefine them. It still adds useful semantic guidance by establishing a source precedence order (url preferred, then draftId, then content as text) and by explaining that targetQuery overrides automatic query detection. This is meaningful value beyond the schema descriptions.

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 and resource ('Refreshes one piece of content'), defines the scope as existing brand content, and explicitly distinguishes itself from create_content_brief. An agent can tell exactly what this tool is for without opening the 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?

Explicitly says to use this tool, not create_content_brief, when the user wants to update or improve existing content. It also states that a source is required, lists the acceptable source types in preference order, and instructs the agent to ask the user which page or draft to refresh when no source is given.

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