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

The readOnlyHint annotation already signals safety, but the description adds substantial behavioral context: results are capped per response, the payload includes count/total/has_more, answered/unanswered counts are census-wide rather than page-wide, null disposition has a specific meaning, and the data records nothing about who flagged. These are genuinely useful behavioral details beyond the annotation.

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 five dense sentences, each adding distinct value: core purpose, response shape, census semantics, null-disposition meaning, and read-only reassurance. It is front-loaded with the primary purpose and contains no filler or redundant restatement of the tool name.

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?

Given there is no output schema and zero parameters, the description carries the full burden of explaining the return value and behavior. It covers the main response fields, pagination semantics, and subtle interpretation of null disposition. Minor gaps remain, such as the exact cap value and the detailed shape of each flagged target entry, but the description is otherwise complete for a zero-argument read-only 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?

The tool has zero parameters and the input schema is an empty object, so the schema leaves nothing undocumented. Per the baseline for zero-parameter tools, this receives a 4; the description appropriately avoids inventing parameter details that do not exist.

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 clearly identifies the resource ('flagged targets') and what is included ('with the maintainer's answer where one exists'), but it lacks an explicit verb such as 'list' or 'fetch'. It provides enough substance to distinguish this from related tools like flag and dispose_flag, though it does not name them.

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 implies this is the correct tool for viewing flagged targets along with maintainer answers and pagination metadata, but it never explicitly states when to use it versus alternatives. There is no direct 'use when' or 'instead of' guidance, leaving the agent to infer the selection context from the resource description.

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