Get Group Posts

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

The annotations already declare readOnlyHint=true, so the description need not restate that. The description adds the concept of 'recent' posts, implying time-based filtering, but does not disclose additional behaviors like pagination, rate limits, or ordering specifics beyond the schema. No contradiction with annotations; it provides some value but not rich behavioral context.

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?

The description is a single, concise sentence that front-loads the action and resource. Every word contributes to meaning, with no redundant or filler content. It is appropriately sized for the tool's simplicity.

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 simple read-only list tool, the description is minimal but adequate, especially with readOnlyHint=true and a complete input schema. The output schema likely covers return structure, so the description need not elaborate. However, it omits any mention of ordering or default limits, though these are implicit in the schema. It is complete enough for a straightforward operation.

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?

The input schema fully documents both parameters (group_id and max_posts) with descriptions, achieving 100% schema coverage. The tool description does not add any extra semantic meaning beyond what the schema already provides, so it relies on the schema as the baseline. No additional clarification is offered.

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 tool retrieves recent posts from a group feed, using a specific verb ('Get') and resource ('group feed'). It naturally distinguishes from sibling tools like get_page_posts and get_user_posts by the group context. No ambiguity.

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 alternatives such as get_page_posts or get_user_posts. The description does not mention any exclusions, prerequisites, or conditions that would help an agent choose it over other post-retrieval tools. This is a clear gap given the many sibling tools.

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