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

Annotations already declare readOnly/idempotent/openWorld=false, and the description adds genuinely new context: 30 posts per page, cursor round-tripping via next_cursor, and the fact that results are limited to what the calling account can see. Missing only ordering/rate-limit detail to reach a 5.

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?

Front-loaded with purpose, then result shape, then pagination, then visibility — a sensible order with no throwaway sentences. Slight redundancy between 'as its search box does' and 'Runs the group's search box' costs it the top score.

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 does the work of describing returns (post titles/text with author and preview, members by name) and pagination, so an agent can call it and page correctly. Course result shape is left unspecified, a minor gap.

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 baseline is 3; the description earns above that by stating the default type (posts) and explaining the pagination contract ('pass next_cursor back as cursor'), which clarifies how the cursor parameter is actually obtained and reused.

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 ('Search a group's posts, members or courses') and anchors the scope to a single group, which implicitly separates it from list_posts/list_courses/search_members. It does not explicitly name those siblings, so it stops just short of a 5.

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 'as its search box does' framing and the visibility note imply when this is the right tool, but there is no explicit guidance on when to prefer it over search_members, list_members, list_posts or list_courses. Usage is inferable rather than stated.

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