List reported posts

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

The annotations already establish read-only, idempotent, non-destructive behavior, while the description adds meaningful context: the posts are member-reported and awaiting review, and access is restricted to admins and moderators. It does not cover pagination or return shape, but it adds authorization and queue-state context beyond the structured annotations.

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 short and front-loads the reported-queue purpose, with the delete_post alternative included efficiently. It repeats the admin/moderator restriction twice, which is minor redundancy but not harmful.

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 one-parameter read-only listing tool with full schema coverage and clear annotations, the description supplies the essential queue, authorization, and removal-alternative context. It does not describe return values or pagination, but no output schema exists and the core behavior is adequately specified.

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 single group parameter is fully documented in the schema. The description does not add parameter-specific meaning beyond that, which is acceptable given the complete schema 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 uses a specific verb and resource: it lists posts in the group's Reported queue that members flagged. It also distinguishes the tool from delete_post by noting that delete_post removes one, so an agent can route removal actions elsewhere.

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?

It clearly states the queue context and that the tool is for admins and moderators only, and it points to delete_post for removal. It does not explicitly say when not to use it versus list_posts, but the reported-queue scope makes the intended use clear.

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