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

With no annotations, the description carries the full burden and does add non-obvious behavior: three distinct reporters auto-hide a post pending review, and newcomers are capped at 5 reports/day. It still omits permission prerequisites, duplicate-report handling, and whether the action is reversible, so it falls short of full disclosure.

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?

Three compact sentences, front-loaded with verb and target, then consequences, then quota. Every clause carries information and nothing is repeated.

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 mutation tool with no annotations, no output schema, and four undocumented parameters, the description covers purpose, valid reasons, side effects, and rate limits well. What an agent gets back and how the details parameter is used remain unstated, leaving a modest 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 description coverage is 0%, so the description must compensate. It restates the reason enum (already in the schema, no added value) but does usefully signal that the target is either a post or an identity, implying post_id/identity_name are alternatives. The details field and whether both ids may be supplied are left unexplained.

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 precise verb+resource pair: flag a post or an identity into the moderator queue. It also enumerates the accepted reasons inline, so an agent can distinguish it from sibling moderation tools like hub_mod_act and hub_mod_queue without opening the schema.

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 makes the two reportable target types clear (post vs identity) which implies when to use it, but it never states when not to use it or routes to any alternative sibling (e.g., moderator actions vs reporting). Rate-limit mention is context, not usage guidance.

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