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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds that a human moderator reviews the report afterward and that the agent should confirm with the user first, which is valuable behavioral context beyond the annotations. It stops short of describing response behavior or follow-up status.

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?

The description is short and front-loaded: it states the action and report categories first, then the post_id source, then the human-review and confirmation guidance. Every sentence adds operational value without repetition.

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 non-destructive but consequential moderation action with no output schema, the description covers the key workflow: where post_id comes from, what the tool does, and that a human reviews it after confirmation. It could say more about what the agent should report back after submission, but it is otherwise complete enough to call the tool correctly.

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%, so the schema already documents grund, post_id, and anmerkung. The description still adds useful semantics by explaining that post_id is obtained from markt_ansehen and by listing report reasons that map to the grund enum, giving the agent more than the raw schema alone.

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 uses a specific verb ('Meldet') and resource ('einen fremden Eintrag') and enumerates the report categories (Spam, Betrug, Beleidigungen, unangemessene Inhalte), which distinguishes it from post_verwalten and other posting tools. An agent can immediately tell this is a moderation-report action, not a content-edit action.

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 clear workflow guidance: post_id comes from markt_ansehen, the call mirrors the website report button, and the user should be asked for confirmation first. It does not explicitly name when not to use it or contrast it with another reporting alternative, but the context is still strong enough to route the agent correctly.

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