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

Goes meaningfully beyond the sparse annotations (readOnlyHint=false only) by warning that the call is a WRITE that changes stored state and is not safe to repeat blindly (non-idempotent), plus an auth constraint and the fact that the reason is publicly visible. It stops short of saying whether a disposition can be changed later or what state the flag ends in.

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 tight sentences with the auth constraint and purpose front-loaded, then the write warning. No filler, though "not safe to repeat blindly" is slightly informal phrasing for a behavioral caveat.

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 5-parameter write tool with no output schema and 0% schema coverage, the description covers purpose, auth, idempotency, and reason visibility, but leaves the target parameters and secret unexplained. An agent could call it, but the parameter surface is under-described.

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 carries the full burden, yet it only touches the reason (public, required) and repeats the disposition enum values. target_type, target_id, and the undocumented secret parameter receive no explanation of format, meaning, or role.

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 and resource: recording a disposition (no-action/acted/watching) against a flagged target. An agent can tell what the call does, but the description never names the related siblings (flag, flags, moderate, moderation_state) to disambiguate which one to pick.

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?

"Maintainer only" establishes the authorized caller, which implies the usage context, but there is no explicit when-to-use versus alternatives guidance and no when-not-to-use guidance. Usage is inferable rather than stated.

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