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

Annotations already establish read-only, idempotent, closed-world safety, so the description's job is to add context beyond that – and it does, disclosing provenance (items handed over by the GEO agent when the brand is absent from a topic) and that each idea carries justifying evidence. It says nothing about volume, staleness, or what happens when the queue is empty, but the output schema covers the response 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 resource definition and provenance are front-loaded in one efficient sentence, with the reading-order advice second. The closing clause ("the cheapest useful work available") is persuasive framing rather than information, but it is short and does reinforce prioritisation.

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 an output schema covering return shape, annotations covering safety, and full schema coverage on both parameters, the description supplies exactly the missing piece: what these ideas are and where they come from. Only the relationship to sibling read tools remains unaddressed.

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 100% and both parameters are fully documented in the schema (limit semantics and workspaceId fallback). The description adds no syntax or defaulting detail beyond what the schema already provides, so baseline 3 applies.

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 the specific resource (content ideas briefed but not yet written) and its scope, which clearly distinguishes it from the writing/mutation siblings like generateArticle or briefContentGap. It does not, however, distinguish itself from near-neighbours such as readWaitingItems or readOpportunities, so an agent must infer the boundary.

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 ordering guidance ("Read this FIRST") and a rationale (writing an already-briefed topic is cheap wins), which implies when to use it. But there are no explicit alternatives, no exclusions, and no statement of how it relates to readWaitingItems or readTopics.

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