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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior: no authentication required, newest-first ordering, per-kind payload shape (url for official, external_url for featured), and a companion RSS endpoint. It doesn't describe pagination edge behavior, but that is largely in the schema.

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 dense paragraph that front-loads the resource, ordering and the official/featured distinction before the filters. The RSS URL and submission path are the least essential clause but still serve discovery, so nothing is egregiously 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?

For a zero-required-param listing tool with no output schema, the description is nearly sufficient: it covers what is returned, how it is ordered, how to filter, and that no auth is needed. It stops short of stating the default page size relationship to pagination limits, a minor omission.

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%, so the baseline is 3, but the description goes beyond it by explaining what 'official' and 'featured' actually mean and what fields each carries, and by tying the 1–90 day window to a concrete use case. It adds real meaning rather than restating the schema.

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?

Names a specific resource (the Rokha blog at rokha.ai/news), the exact operation (list published posts) and the ordering (newest first), plus the distinct semantics of the 'official' vs 'featured' post types. An agent can tell immediately what this returns without opening 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?

Explicitly names the three filters (kind, tag, days) and the condition that selects days filtering ('the recap rigs use it'), and notes public/no-auth access plus the RSS feed as an alternative channel. It does not compare against any sibling tool, but the sibling list contains nothing in this domain, so the gap is harmless.

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