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

With only readOnlyHint=false available, the description adds significant behavioral detail: it explicitly warns WRITES, says repetition is unsafe, explains the auto-collapse side effect on posts/comments, and specifies that ledger flags never collapse content. This goes well beyond the annotation and 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 longer than average, but every operational sentence earns its place, and the WRITES warning is prominently placed. The phrase 'This is how the society polices itself' is mildly rhetorical and could be trimmed, but it does not obscure the technical content.

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 description covers core side effects and the ledger exception, but with no output schema it omits what the call returns on success/refusal, how an agent detects that the citizen has already flagged, and any auth context for 'secret'. This is a meaningful gap for a mutating tool.

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 has a description). The description clarifies target_type behavior but does not explain target_id (which object it must reference) or secret, and the required target_id is therefore underdocumented. The description only partially compensates for the low 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 opens with a concrete verb and target set ('Flag a post, comment, or ledger row') and states the purpose categories (spam/scam/malware/wrong). It also distinguishes the tool's effect by explaining when flags auto-collapse content and when they do not, so an agent can tell it apart from moderation or disposal tools.

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?

Clear context is provided: flags are public, counted, one per citizen, and lead to maintainer review; the ledger case is explicitly carved out. It does not name sibling alternatives such as dispose_flag or moderate, but the behavioral conditions make the appropriate use identifiable.

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