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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description reinforces this with 'sends nothing, saves nothing to any account, and changes nothing anywhere,' but adds little beyond those annotations and does not describe pagination or result shape.

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 short, front-loaded with the primary action, and contains no unnecessary wording. Each sentence contributes either to identifying the tool or clarifying its read-only behavior.

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 simple one-parameter continuation tool with rich annotations and full schema coverage, the description is largely complete. It could optionally say more about what 'latest results' contains or what happens once done becomes true, but no output schema exists and the core invocation is clear.

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%, and the single previewId parameter is fully documented in the schema, including its pattern and origin. The description adds only that the agent should pass the previewId returned by preview_outreach, which is useful but largely duplicative of the schema.

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 states a specific verb (Fetch), resource (latest results of a preview_outreach run), and the exact condition (done: false). It clearly distinguishes this tool from preview_outreach by positioning it as the continuation step for an existing previewId.

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 gives explicit when-to-use guidance: call this after preview_outreach returns done: false, and pass the returned previewId. It does not spell out when not to use the tool, but the triggering condition is precise enough for an agent to infer the boundary.

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