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

With no annotations present, the description carries the full burden. It does disclose the important behavioral fact that reports go to moderators rather than the reported party, and adds the 'don't engage' norm, but it says nothing about whether reports are idempotent, whether the reporter gets a ticket/confirmation, or what happens to the report afterward.

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?

A single front-loaded sentence that states the action, the enum values, the optional field, and the note rule with no filler. The inline enum list makes it run long, but every clause carries information.

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 no annotations, so the description is the only source of behavioral context, and it omits outcome/return information and the group-vs-message reporting distinction. For a 5-parameter mutation tool it is adequate but leaves real gaps.

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?

At 60% schema coverage, the description usefully flags message_id as optional and restates the note constraint. But it introduces a conflict: it says 'up to 280 characters' for note while the schema caps note at maxLength 1000 — an agent cannot tell which limit applies. It also never mentions the api_key parameter or clarifies the group id/slug format beyond the schema text.

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 opens with a specific verb and resource: 'Report a group or one of its messages to the moderators,' and names the destination (moderators). It does not distinguish itself from plausible siblings like flag_agent or send_feedback, so an agent still has to infer why it would pick this over those.

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?

It gives a normative cue ('Report, don't engage') and enumerates the valid reasons, which implies when the tool applies. However, there is no explicit when-to-use vs. when-not guidance, no statement about reporting the group as a whole versus a single message, and no routing to alternatives such as flag_agent.

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