get_group_feed

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

No annotations provided; description only states a get operation (read) without disclosing any behavioral traits such as error conditions, authentication requirements, or side effects. Minimal disclosure for a read operation.

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?

Description is two sentences plus concise arguments list. No redundant words, front-loaded with purpose and important note, well-structured.

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 tool with 2 required parameters and an output schema, the description covers purpose and parameter sourcing. Could be improved by noting the return format (e.g., list of posts), but overall complete for basic usage.

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?

With 0% schema description coverage, the description adds meaning by stating that school_id is the same as used in list_groups and group_id comes from list_groups results. This provides relational context beyond the schema types.

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?

Description clearly states 'Get posts from a specific group's feed', which is a specific verb+resource. It distinguishes from siblings like get_feeds (general) and list_groups (listing groups, not posts).

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?

Description emphasizes that both school_id and group_id are required, and explicitly links school_id to list_groups and group_id to its results, providing clear context. However, it does not mention when not to use this tool or alternative tools.

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