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

Annotations only mark readOnlyHint=true, but the description adds substantial behavioral detail: which fields every brief carries, which fields are article-specific, the effect of compact, and the exact hasBrief/briefStatus/queuedUntil shape returned when a brief does not exist. It also explains the meaning of 'queued' and the daily-cap reset timing. This goes far beyond the structured annotations and is internally consistent.

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?

Every sentence earns its place. The purpose is front-loaded first, then channel selection, then the payload fields, then the missing-brief status behavior. The description is information-dense but well-ordered, and none of it is redundant with the schema or annotations.

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 correctly takes on the burden of explaining return values: hookStatement, keyStats structure, always-populated fields, and the full missing-brief response. It also covers the unusual queue-forging state, which an agent would otherwise be unable to interpret. The description is complete for a retrieval tool with this parameter set.

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 compensate, and it does for channel and compact: channel values are enumerated with 'article default' clarified and compact's effect on referenceArticles is stated. suggestionId is not explicitly described, but its role is clear from the opening sentence and the schema's UUID format. This is strong compensation, though not exhaustive for every parameter.

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 opens with a specific verb and resource: 'Get the full content brief for an article suggestion.' It clearly distinguishes this from siblings like generate_article_brief by framing itself as retrieval of an existing brief and detailing per-channel behavior. The description makes the tool's scope obvious without requiring 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?

The description gives clear context on how to use the tool: pass channel to select a channel brief, pass compact=true to drop referenceArticles, and poll after queuedUntil if the brief isn't ready. It does not explicitly name alternatives or exclusion cases, such as 'use generate_article_brief to create a missing brief,' so it falls short of a 5. Overall, an agent knows when and how to call this tool correctly.

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