List posts

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

Annotations already cover the read-only, idempotent, non-destructive profile, so this description wisely adds behavior they don't: page size cap of 30, the pinned-then-newest ordering, the non-obvious pagination-plus-filter interaction, and that preview is truncated to 200 characters. That last detail prevents an agent from assuming it got the full post body.

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?

Three sentences, each earning its place: the first states purpose and ordering, the second pagination and the filter caveat, the third the preview/get_post split. Front-loaded with the core purpose, no redundant restatement of the name or title.

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 carries the return-shape burden and does so — author, category, likes, comment count, and truncated preview. Combined with the pagination caveat, an agent has everything needed to call this correctly and interpret a short page.

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 100%, so the baseline is 3, but the description adds real meaning: the relationship between next_cursor and the cursor parameter, and the crucial caveat that category/since apply only within the current page rather than across the feed. Slightly short of 5 only because limit's default and range are left to 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 and resource ('Lists one page of the group's feed') plus the exact ordering semantics: pinned first, then newest. It also names the complementary tool (get_post) and what it returns, so the agent can distinguish this listing tool from full-post retrieval.

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?

Explicitly says to pass next_cursor back as cursor for older posts, warns that category/since filter within the page so results can be short or empty while next_cursor still points further, and routes to get_post for full text. Conditions and alternatives are spelled out rather than implied.

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