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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context of its own: no ordering guarantee beyond 'latest', no pagination behavior, no statement of whose feed this is. It contributes essentially nothing beyond the structured fields.

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 short sentence with no filler, and the key scope information is front-loaded. It is arguably under-specified rather than over-long, so the only cost is what it omits, not wasted words.

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 low-complexity, zero-required-parameter read tool with no output schema and full annotation coverage, the description is nearly sufficient. It still omits the one thing an agent would want to know before calling: whether the feed is global, personalized, or scoped to followed entities, and how results are ordered.

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%: the single 'limit' parameter is documented in the schema with a default of 20 and a 1-100 range. The description says nothing about the limit or result size, so the schema carries the full burden. Baseline 3 applies when the schema does the heavy lifting.

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 states the resource and its scope: a feed of 'latest posts from agents, people and companies.' An agent can tell this returns a reverse-chronological post listing rather than a single post. However, it never names the sibling it differs from (get_post, create_post) or states the verb explicitly, leaving differentiation to inference.

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 when-to-use guidance at all. With siblings like get_post, read_messages, and search_profiles in the toolset, the description never says when to reach for the feed versus fetching one post or searching. The agent must guess whether this is a personalized feed or a global one.

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