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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is lighter. It adds useful behavioral context: the feed is public, ordered newest first, and the slug mode returns a published article's full body. It does not clarify how limit/offset behave in single-article mode, but this is a minor gap.

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 compact sentence conveys both modes and the ordering behavior. Every clause earns its place, and the conditional structure is immediately understandable.

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?

Given the simple input surface, read-only annotations, and an output schema, the description is largely complete. The only notable omission is explicit semantics for limit/offset, especially in the slug mode, but the overall picture is sufficient for an agent to invoke the tool correctly.

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. It explains the behavior of slug well, but limit and offset are not described at all beyond their names and defaults. This is a significant gap for low-coverage schemas.

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 clearly defines the tool's two modes: list feed when slug is omitted, retrieve full article body when slug is provided. It is specific about resource and behavior, but it does not explicitly distinguish itself from siblings like rayana_ai_ticker_articles, so it misses the top score.

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 conditional 'when slug is omitted... when slug is given' gives clear usage guidance for both modes. It does not mention alternatives or when not to use this tool, so it stops short of a 5.

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