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

Annotations already declare the mutation and open-world profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description usefully adds the required auth scope 'boards:report'. However, it says nothing about what happens after a report — whether the post is hidden, who sees the reason, or whether duplicate reports are merged — which is the key behavioral question for a moderation tool.

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 short sentences, front-loading the action and following with the scope requirement. Nothing is wasted, though the second sentence is a bare constraint rather than integrated context.

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 mutation tool with no output schema, the definition covers the action and the auth scope, which is the minimum. It omits the outcome of the report, any rate or duplicate-report behavior, and guidance on the reason field, leaving meaningful gaps for a moderation action.

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%: only idempotency_key is documented, and that documentation lives in the schema, not the description. The description adds no meaning for post_id or reason, leaving the agent to infer what 'reason' should contain and how it is surfaced.

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 ('Report a public post to the operator'), which is clear and distinguishable from siblings like redact_board_post or delete_content. It does not explicitly name those siblings, so the differentiation is left implicit.

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?

'Report a public post to the operator' implies the use case (flagging content for moderation review), but there is no explicit guidance on when to prefer this over redact_board_post or delete_content, and no stated preconditions beyond the scope requirement.

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