flag

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it discloses nothing: no permission requirements, no note on whether a flag is reversible or reviewable, no rate limits, and no indication of what happens after a flag is submitted. For an unannotated mutation tool this is a serious gap.

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?

Two terse sentences, front-loaded with the action and followed by the key constraint on 'kind'. Nothing is wasted, though the extreme brevity is part of the under-specification problem.

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?

An output schema exists so return values need not be explained, but for a three-required-parameter mutation tool with no annotations and 0% schema coverage, the description omits permissions, side effects, and two of three parameter meanings.

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 for three required parameters. It usefully enumerates the 'kind' values ('threads' or 'posts'), which the schema does not, but says nothing about what object_id refers to or what form 'reason' should take.

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 states the action ('Flag abuse') and names the accepted kind values, so an agent can tell it apart from sibling write tools like vote or reply. However, it never says what object is being flagged in plain terms, leaving the resource only inferable from the 'kind' hint.

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?

There is no statement of when to use this tool versus siblings such as vote, reply, or set_canonical, and no prerequisites or conditions are given. The agent must guess the appropriate context from the name alone.

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