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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description does add real behavior beyond that: result ordering ('newest first'), the difference in payload size (feed summary vs 'full body'), and the restriction to 'published' articles. It omits pagination behavior and what happens for an unknown or unpublished slug, so it is adequate but not rich.

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?

A single sentence that front-loads the default behavior (feed, newest first) before the conditional override. Every clause carries information and nothing is wasted.

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 present, return-value detail is unnecessary, and the description covers the key behavioral branch plus ordering. The remaining gap is pagination semantics for limit/offset, which matters for a feed tool but is minor relative to what is stated.

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 carry parameter meaning; it explains `slug` well (omitted = feed, given = single article) but says nothing about `limit` or `offset`, leaving two of three parameters undocumented anywhere. It partially compensates for the coverage gap rather than fully closing it.

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 resource (public articles feed / a single published article's body) and the condition that switches between the two modes. It is clear and specific, but it never distinguishes itself from the sibling rayana_ai_ticker_articles, which an agent could easily confuse with this tool.

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 tells the agent which mode is selected by the presence or absence of `slug`, which is genuinely useful routing within the tool. However, it gives no guidance on when to prefer this tool over rayana_ai_ticker_articles or rayana_ai_search, so alternative selection is left to inference.

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