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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond that: the cost model ('1 point per returned record') and the returned field set, which lets an agent reason about budget and output shape.

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?

Two compact sentences that front-load what the feed contains, then append the cost note. No filler, and the most decision-relevant content (modes and fields) leads.

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 no output schema, the description usefully names the fields returned (author, upvotes, comment counts) and discloses cost, which is enough for a 4-param read-only feed tool. Minor gaps remain around pagination and whether results are ranked or chronological under 'newest'.

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% and all four parameters (date, sort, period, max_items) are fully documented in the schema with enums and bounds. The description only loosely echoes the sort/period values and adds no syntax or constraint detail, 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?

States a specific verb and resource ('Indie Hackers post feeds') and enumerates the two sort modes and available periods, plus the returned fields (author, upvotes, comment counts). It's clear what the tool fetches, though it does not explicitly distinguish itself from the sibling run_indiehackers_posts or run_indiehackers_ideas_search.

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 implied rather than stated: an agent can infer that 'top' pairs with period and 'newest' ignores period, but the description never says when to choose this tool over run_indiehackers_posts or how the search variant differs. No exclusions or prerequisites are given.

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