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

Adds behavior beyond the annotations by disclosing that requests are reviewed by an admin and never applied on their own, plus the dual authentication paths (Turnstile for browser forms, API key for programmatic callers). This materially affects how an agent should call and reason about the tool, and it does not contradict destructiveHint=false.

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?

Three dense sentences, front-loaded with purpose, then semantics, then auth. No filler, and each sentence carries distinct 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?

With no output schema, the description covers the key unknowns for a submission-style tool: review/reversibility semantics and the two auth routes. It omits what a caller receives after submitting and any rate-limit or duplicate-submission constraints, but is otherwise complete enough to invoke 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 low (29%), but the description only partially compensates: it clarifies the kind/timing distinction and newStartDate for rescheduled requests, and hints at turnstileToken via the Turnstile mention. It says nothing about slug, message, website, or contactEmail, leaving several parameters undocumented in both places.

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 ('Report an issue with an event listing') and enumerates the concrete issue kinds (wrong, gone, cancelled, postponed, rescheduled). It is clearly distinguishable from siblings like submit_event, which handles creation rather than correction.

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 real usage context: anyone may flag, an admin reviews every request, nothing is auto-applied, and it distinguishes browser (Turnstile) from programmatic (API key) callers. It stops short of naming a sibling alternative or a when-not-to-use condition, so it's strong but not exhaustive.

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