Get Mod Queue

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

No annotations are provided, so the description carries the full burden. It discloses the JSON return format (items with kind, meta with limit/has_more/next_cursor), pagination via next_cursor, and item kinds. It also mentions the related action tools, providing useful behavioral context beyond the schema.

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 three sentences with no fluff. It front-loads the purpose, then describes the return format and next steps. Every sentence earns its place.

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?

The tool has no output schema and no annotations, so the description must provide context. It covers purpose, return shape, pagination, and follow-up actions. A minor gap is not explicitly stating the moderator permission requirement, but it's implied by 'mod queue'.

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 schema already describes all 4 parameters with 100% coverage, so the baseline is 3. The description adds minimal parameter-specific information, only referencing 'next_cursor' and 'fullname' in context, which doesn't significantly enhance the schema's parameter descriptions.

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 states 'List posts and comments awaiting moderator review in a subreddit's mod queue', using a specific verb and resource. It distinguishes from sibling tools by naming the 'mod queue' as a distinct Reddit feature, even though related queue tools exist.

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 provides clear context for when to use the tool (mod queue) and suggests a follow-up action: 'Use reddit_approve/reddit_remove with an item's fullname to act on it.' It doesn't explicitly exclude alternatives like reddit_get_reports, but the mod queue context implies a combined view.

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