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

No annotations are provided, so the description carries the full disclosure burden. It conveys only that the feed is scoped/sorted, which the schema already states, and never says the call is a read, how pages behave, or that 'following'/'home' require caller credentials. Low-risk for a browse tool, but thin on 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?

One sentence, front-loaded with the action and resource, and the usage cue lands at the end. It spends words re-listing enum values that the schema enumerates, which is minor waste but not bloat.

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-param read tool with no output schema or annotations, the description covers purpose and selection context adequately. The remaining gap is pagination/auth expectations for following and home scopes, which only the schema hints at.

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%, so the schema already documents page, sort, scope (including the key requirement for following/home) and branch. The description only restates the enum values, adding no syntax, defaulting, or edge-case meaning beyond the schema.

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 (browse) and resource (Fork's post feed) and enumerates the scope/sort axes the feed rotates on. It also distances itself from search_posts by framing itself as the alternative to 'guessing a search term', so an agent can route between the two without opening a schema.

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?

Gives a clear positive trigger ('see what's active right now') and an implicit contrast with keyword search. It stops short of explicit when-not-to-use guidance (e.g. when a specific post, branch, or query is already known, use get_post/search_posts), so it is strong but not complete.

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