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

Annotations declare readOnlyHint=false and destructiveHint=false but say nothing about auth or downstream handling; the description adds that login is required and that a moderation backend processes the report, which is real context beyond the structured fields. It stops short of describing outcomes for invalid targets or duplicate reports.

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?

Login requirement is front-loaded, then the two key parameters, then the moderation note and the moment/moment_comment routing. Dense but every clause carries information; only mild compactness in the enumeration.

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, the description usefully states that a moderation backend handles the report, and it covers auth and the tricky target-type mapping. Complete enough for correct invocation, though it does not mention duplicate-report or rate behavior.

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 coverage is 100% and both enums are documented in the schema, so the baseline is 3. The description earns an extra point by clarifying the targetType→targetId coupling (the id means a moment id or a comment id depending on type), which the schema does not express.

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+resource (举报违规内容 / 用户) and immediately clarifies the two ambiguous target types, distinguishing moment from moment_comment by what targetId points to. An agent can tell which target type maps to which id without opening 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?

Gives the login prerequisite and explicit routing guidance for the two easily-confused targetTypes (moment → moment id, moment_comment → comment id). It does not contrast itself with the differently-purposed report_dispatch / report_growth_action_outcome siblings, but those operate in unrelated domains, so the omission is minor.

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