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

Annotations already declare that this is a non-read-only, destructive, non-idempotent, open-world operation. The description adds valuable behavioral context beyond that: missing targets return 404 without consuming quota, flags share a 20-per-UTC-day comments-and-flags quota, and flags are logged publicly.

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?

Three short sentences, front-loaded with the core action and followed by only operationally useful constraints. Every sentence earns its place with no filler.

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 reasonably rich annotations, the description covers purpose and key behavioral constraints. However, it leaves parameter semantics incomplete for target_id and target_type, which matters because schema coverage is low and an agent needs to know how those two fields relate.

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%, with just the reason parameter documented. The description names the target types, but that duplicates the schema enum and does not explain target_id, how it relates to target_type, or add any meaning beyond the schema's type and constraint definitions.

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 a specific verb (Flag) and the exact resources it applies to (listing, comment, or merchant) plus the intended outcome (maintainer review). This distinguishes the tool from siblings like comment or vote without the agent needing to open the schema.

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 by the stated purpose: use this to report content for maintainer review. However, the description gives no explicit when-to-use guidance, no when-not-to-use conditions, and does not name an alternative sibling such as comment or vote.

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