Posts from one group

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the scoping detail of group-specific feed, but does not describe pagination behavior or return format. This is acceptable given annotations, but no additional behavioral traits are disclosed beyond what the title/schema imply.

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, well-structured sentence. It front-loads the core purpose ('Posts belonging to a specific ParentSquare group') and includes a practical pointer to list_groups. No redundant or filler content.

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 tool with an output schema and strong annotations, the description covers the essential purpose and ID sourcing. It does not explain pagination, but the schema provides the page parameter details. Overall, it is sufficiently complete for an agent to select and invoke correctly.

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% with descriptions for both 'group_id' and 'page'. The description adds value by telling users to get group IDs from list_groups, which clarifies the source of the required parameter. Page semantics are left to the schema, which is sufficient given high coverage.

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 posts for a specific ParentSquare group, with a specific verb ('Posts belonging to') and resource ('group'). It distinguishes itself from siblings like 'get_feeds' by emphasizing 'a specific group' and references 'list_groups' for IDs, removing 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?

The description implies usage: to get posts for one group, use this tool, and to find group IDs, use list_groups first. It does not explicitly exclude alternatives like get_feeds, but the phrasing 'a specific ParentSquare group' contrasts enough to guide selection.

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