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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not say where the report goes, whether it is reversible, whether it notifies the author, or how duplicate reports behave despite idempotentHint being set.

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 compact, front-loaded sentence with no filler typical of over-written descriptions. It does spend words restating the enum values already in the schema, which is minor redundancy rather than harm.

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?

No output schema and annotations cover most behavioral traits, so the bar is lower, but the undefined 'note' parameter and the total absence of outcome/error information leave a real gap for a mutation tool.

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% and the description only echoes the reason enum already present in the schema. The third parameter, 'note' (a 200-char string), is never mentioned at all, so an agent gets no guidance on what belongs in it or whether it is visible to moderators.

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 ('report') and resource (a post) plus the taxonomy of valid reasons, which clearly separates it from siblings like delete_post or favorite. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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 intent ('use this to flag bad content') is implied by the enumerated reasons, but there is no explicit guidance on when to report versus when to use delete_post, whether you can report your own post, or what happens after reporting. Usage is inferable but not stated.

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