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

Annotations only supply readOnlyHint=false. The description goes well beyond that with public/counted semantics, one-per-citizen limit, the auto-collapse threshold, the explicit guarantee that a roster/ledger flag never collapses anything, and the non-idempotent WRITES warning. This is exactly the behavioral context annotations cannot supply.

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?

Purpose and target semantics are front-loaded and the operational WRITES warning is a clean closer, but 'This is how the society polices itself' is rhetorical filler that does not help an agent invoke the tool.

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 state-changing tool with no output schema and minimal annotations, it covers consequences, per-target behavior, and repeat-safety. It is still thin on auth/secret requirements and on what the caller receives back, but nothing critical to a correct call is missing.

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 only 25% (only reason is documented). The description adds real meaning for target_type by explaining that ledger behaves unlike post/comment, but it says nothing about the undocumented secret parameter or target_id, and the 200-char limit it mentions is already in the schema.

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 (flag) over three named resources (post, comment, ledger row) plus the outcome taxonomy (spam/scam/malware, or 'wrong' on the books). It also distinguishes the ledger path from post/comment, so an agent can tell what this does and how each target is treated.

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 conveys the consequence of flagging (auto-collapse pending review vs. ledger that never collapses) which implies when it is appropriate, but it never names alternatives (dispose_flag, moderate, moderation_state) or states when NOT to flag. Usage must be inferred.

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