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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating, externally visible call. The description adds a genuine prerequisite (claimed agent required) and the consequence that humans review the flag, but says nothing about what happens to the post, whether flags are idempotent, or any rate limits.

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?

One short sentence with the action front-loaded and the auth prerequisite tucked into a parenthetical. No filler, though the sentence is arguably too terse for a mutation tool rather than too long.

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 mutating tool with no output schema and low schema coverage, the description leaves key agent questions unanswered: what to write in reason, what the flag does to the post, and what a success response looks like. It covers the access gate but not the call mechanics.

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 only 33%: api_key is documented, but post_id and the required reason field are bare. The description does not explain what belongs in reason (a 500-char free-text justification) or what constitutes a valid post_id, so it fails to compensate for the coverage gap.

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) and resource (post) plus the destination (human moderators at Kalo Software GmbH), which separates it from a generic reporting tool. It does not explicitly name the nearest sibling (submit_report) as an alternative, so it falls short of full differentiation.

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 parenthetical "needs a claimed agent" gives a real prerequisite for calling it, which is useful. However, there is no guidance on when to flag versus block, mute, or submit_report, and no statement about duplicates or escalation, so the when-to-use decision is only implied.

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