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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral information beyond them: the dossier is 'source-backed' and it 'returns not_found when no dossier has been generated yet', which tells the agent to expect and handle an empty state.

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 the core action and followed by the contents list and the usage triggers. The middle enumeration is long but each item is a distinct payload the caller cares about; no sentence is filler. Minor cost is that the dense list slightly dilutes front-loading of the usage trigger.

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?

There is no output schema, so the description carries the burden of describing the return payload — and it does, by naming the dossier sections and the not_found failure mode. Combined with rich annotations and a fully documented single parameter, the agent has enough to call this correctly; only the exact response shape remains unspecified.

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 the single parameter's schema entry already explains that trend_id is a numeric id 'from list_trends or search_trend_insights', including its provenance. The description adds nothing further about the parameter (no format, range, or lookup guidance), so the baseline of 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 uses a specific verb and resource ('Get the source-backed dossier for one trend') and then enumerates exactly what the dossier contains: label resolution, dated timeline, evidence coverage, named channels, content landscape, brands and products. That enumeration meaningfully distinguishes it from siblings like get_trend or get_trend_ai_insights, though it never names those siblings explicitly, so the 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 concrete user-intent triggers: 'what a trend is, what happened, where it is being discussed, or what content to publish.' That is clear when-to-use guidance. It stops short of explicit when-not-to-use guidance or directing the agent to the alternative sibling tools when a lighter-weight answer suffices.

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