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

With no annotations, the description carries the full behavioral burden and discloses key traits: moderator-only authorization, the state of held posts (invisible everywhere until released), inclusion of reader reports, and oldest-first ordering. It does not explicitly state read-only safety, side effects, or pagination behavior, leaving a few gaps.

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 short, front-loaded fragments with zero waste. The access constraint leads, followed by the queue contents and ordering, making it easy to parse quickly.

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 zero-parameter tool with no output schema, the description sufficiently covers what the agent needs: who may call it, what the queue contains, and the ordering. No return format is promised by an output schema, and the content summary serves as an adequate return description.

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 tool has zero parameters, so there are no parameter semantics to document. The baseline for zero parameters is 4, and no additional parameter meaning is needed or provided.

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 identifies the resource precisely as the moderation queue and lists its contents (AI-judge-held posts and open reader reports), making its purpose unmistakable. It lacks an explicit verb like 'list' or 'get', but the noun phrase and details clearly distinguish it from sibling moderation tools such as hub_mod_act.

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 gives a clear access prerequisite ('MODERATORS ONLY') and explains what the queue contains, which implies when to use it. It stops short of naming alternatives or when-not-to-use conditions relative to siblings like hub_mod_act.

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