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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the returned payload contents and the default/max window for `last`, which helps the agent anticipate scope and volume.

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?

Two sentences, both front-loaded: the payload description leads, the usage note follows. No filler or restatement of the title.

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?

With no output schema and no parameter descriptions, the description usefully explains the return payload and the `last` semantics. It is slightly incomplete in leaving `brandId` (and its relationship to contentId) undocumented, which matters for a 3-param tool.

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%, so the description must carry parameter meaning. It does well for `last` (default 20, max 100) — notably more precise than the schema's own bounds — and implies `contentId` via 'attached to a content card', but `brandId` is entirely unexplained in both schema and description.

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 (Get) and resource (refine chat messages attached to a content card), and enumerates what comes back: text, refinement IDs, preview status, proposed changes, settings, and total message count. This is clearly distinguishable from siblings like refine_content (which mutates) and review_content_refinement.

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 it to 'resume a conversation or review a saved preview', which gives a concrete usage context. It stops short of naming the alternative sibling (e.g., review_content_refinement) or stating exclusions, so it does not reach a 5.

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