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

Adds real behavior beyond the readOnlyHint annotation: the reply carries count/total/has_more, pagination is capped, answered/unanswered counts are a census over total rather than the page, and null disposition means unanswered. It also discloses that it records nothing about who flagged. The explicit 'READ-ONLY' sentence duplicates the annotation, but the semantic detail is genuinely additive.

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?

Information-dense and reasonably front-loaded, with the resource and ordering stated first. The census/null-disposition sentences are precise but the block is heavier than strictly needed, and the closing READ-ONLY sentence restates the annotation.

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?

With no output schema and no parameters, the description carries the return-shape burden and does so by naming count, total, and has_more. Covers what an agent needs for a read-only listing; only genuine gaps are the pagination cursor and the ordering guarantee of equal-ranked items.

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?

There are zero parameters, so the baseline is 4. The description adds no parameter detail (none exist), but 'capped per response' hints at pagination behavior without exposing a control for it.

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 resource (flagged targets) and what it returns (maintainer's answer where one exists), so the agent knows this is the read side of the flag lifecycle. It does not name the write-side siblings (flag, dispose_flag, moderation_state) it must be distinguished from, leaving that differentiation to inference.

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?

Usage is implied: reading flagged targets, unanswered first, capped per page. There is no explicit when-to-use or when-not, and no routing to siblings like dispose_flag (to answer) or moderation_state (for state), so an agent must infer when this call is the right one.

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