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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuine context beyond them: the content is educational and deliberately not an investment signal, which prevents misuse in a trading context. It does not, however, describe the shape or volume of the returned pattern list.

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?

One compact sentence with an enumerated parenthetical that front-loads the subject matter, followed by the two short scoping clauses (filter, educational disclaimer). No filler, though the parenthetical list is slightly long and could be trimmed.

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 one-parameter, read-only, no-output-schema tool, the description covers purpose, content of each result ('signal to watch and the lesson'), and the caveat about interpretation. It is nearly complete; the only gap is routing relative to viral_attention_quiz.

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?

With a single optional parameter and 100% schema description coverage, the schema already carries the semantics ('Optional platform filter, e.g. TikTok or X.'). The description only repeats 'Optional platform filter' without adding values, matching behavior, or defaults, 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 a concrete resource (patterns of how attention spreads) and enumerates the concrete forms it covers (TikTok sound reuse, quote-post piles, stitch chains, group-chat forwards), plus what each entry contains ('the signal to watch and the lesson'). That is enough for an agent to know what comes back, but it never distinguishes this from the sibling viral_attention_quiz, so sibling differentiation is missing.

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?

Usage is only implied: 'Educational; attention is not an investment signal' hints at the setting (informational/educational queries rather than financial analysis), but there is no explicit when-to-use, when-not-to-use, or pointer to viral_attention_quiz as the alternative for interactive/scored output.

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