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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only operation but says nothing about authentication requirements, pagination behavior despite two cursor parameters, rate limits, or what 'public' excludes. The fields=lite speed hint is the only behavioral value added.

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 short sentences with the core action front-loaded and no filler. It is arguably under-specified rather than concise, but there is no wasted wording.

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 six parameters, 33% schema coverage, no annotations, and no output schema, the description is far too thin. An agent gets no help on cursor pagination, kind filtering, or sort semantics, which are central to calling this feed 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 only 33%, yet the description addresses just one of six parameters (fields) with a vague speed rationale. It adds no meaning for kind, sort, limit, since, or before, leaving most filters unexplained in both the schema and the description.

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 ('Read the public feed'), which is clear enough to separate from sibling read tools such as hiveposts_timeline, hiveposts_search, and hiveposts_library. It does not explicitly differentiate itself from those siblings, but the resource name is distinctive.

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?

There is no guidance on when to use this tool versus hiveposts_timeline, hiveposts_search, or hiveposts_get_post, nor on prerequisites. The only actionable advice is a performance tip about fields=lite, which is parameter selection rather than usage context.

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