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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the description's trailing 'Read-only' is largely redundant. What it adds beyond the structured data is the nature of the sample (random, most-liked public posts) and the usage obligations (attribution, no verbatim copying), which is genuine behavioral context.

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, front-loaded with what the tool returns (sample, source, per-item contents) before the usage instructions. No filler, no restatement of the name or 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, the description does the right thing by stating what each item contains (link plus rationale). Safety requirements for a read-only tool are covered by annotations, and the usage constraints are stated. Only the undocumented count parameter and sampling size behavior leave a small gap.

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 50%: workspaceId is fully documented in the schema, but count (integer, 1-10, default 5) has no description anywhere. The description says nothing about either parameter, so it neither compensates for the gap nor adds meaning beyond the schema; the borderline coverage puts this at the baseline.

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 names a specific resource (a random sample from PumpGTM's library of most-liked public X posts about cold email/DM writing) and states exactly what each item contains (link and reason it was kept). No sibling in the list overlaps with this resource, so an agent can identify it immediately from name plus description.

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 clear positive guidance: use these as references when drafting or critiquing a cold message, credit the author, and do not copy word for word. There is no explicit when-not or named alternative, but this tool has no sibling that could be confused with it, so the routing context is adequate.

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