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

The annotations already signal read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond those annotations: data depth depends on the user's plan, and posts are delayed by 60 minutes without a paid key. It also notes what the posts carry, which gives the agent a better sense of the feed's content.

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?

The description is compact and front-loaded. The first sentence establishes the tool's purpose, and the following sentences provide filtering, depth, and delay details without unnecessary verbiage. Every sentence contributes to correct selection and use.

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 simple three-parameter, no-output-schema feed tool, the description is mostly complete: it covers the feed's contents, filtering, availability, delay, and item-level explanation. It does not mention ordering or pagination, but that is a relatively minor gap for a read-only feed.

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?

All three parameters already have schema descriptions, so the baseline is 3. The description mentions q and categories, but adds only minor meaning beyond the schema, and it does not describe the limit parameter. This is adequate but not additive.

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 identifies the tool as the feed of posts Helious publishes and enumerates the content types: scored releases, auction results, board updates, daily brief, and squawk lines. It is specific about the resource, but it does not explicitly differentiate the feed from closely related sibling tools like get_auctions or get_squawk_sessions.

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 description gives useful usage context: optional q and categories filtering, plan-dependent data depth, and a 60-minute delay without a paid key. However, it does not explicitly say when to prefer this tool over a sibling tool or which tools to use for narrower, topic-specific data.

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