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

Annotations already declare it read-only, non-destructive, and closed-world, so safety is covered. The description adds real behavioral value beyond that: it discloses that blocked and hidden accounts are filtered out, which an agent cannot infer from annotations or schema. It stops short of describing pagination behavior.

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 sentence with no filler, front-loading the resource and then clarifying the scope semantics. The nested parentheticals are slightly heavy but every clause earns its place.

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 no-required-param read tool with no output schema, the description covers content, scope semantics, and filtering behavior well. The remaining gap is pagination — cursor and offset are neither explained nor related to each other, which matters for a 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?

Schema coverage is only 25% (just cursor), so the description must carry weight. It usefully defines the scope enum values ('everyone' vs 'only people you follow plus you'), but says nothing about limit or offset, and doesn't explain how cursor and offset interact. The scope clarification is real added value, but the pagination parameters remain unaddressed.

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 the specific resource (the Home feed) and its contents (recent pours, adds, ratings), so an agent knows exactly what it returns. It implicitly distinguishes itself from personal-activity siblings like list_my_activity by defining the feed as social/global content, but it never names an alternative explicitly.

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?

It explains the two scope modes and which is the app default, which is genuine decision support for the scope parameter. However, it gives no guidance on when to reach for this tool versus related siblings like list_user_activity, search_public_bottles, or explore_catalog, so usage is only implied.

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