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

Annotations only give a minimal profile (not read-only, non-destructive, closed-world). The description adds substantial context beyond them: the fate of the submission (moderation queue), the anti-bot/auth paths, submitter recording, the auto-approval/publish behavior for trusted submitters, and a conditional required field. This is rich behavioral disclosure.

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?

Front-loads purpose in the first sentence and dispenses with filler. The final sentence is a sprawling, multi-clause compound that carries a lot of distinct rules and could be broken up, but no sentence is wasted.

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?

The description is thorough on auth/side-effects for a high-parameter submission tool with no output schema. It leaves the return value (event id, moderation status) unstated and omits semantics for most of the 30 fields, so it is adequate rather than complete.

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?

With 30 parameters and only 17% schema description coverage, the description must compensate, yet it only clarifies organizer_email (optional when signed in, required when anonymous) and implicitly turnstileToken. The vast majority of the 30 fields receive no additional meaning here or in the schema.

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?

Specific verb+resource ('Submit an event') with immediate scope clarification ('for review', 'Goes to the moderation queue'). No sibling tool shares this action, and the moderation-queue detail distinguishes it from any read-only event tools in the sibling set.

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?

Clearly lays out the calling contexts: browser forms use Turnstile, programmatic callers use an API key, signed-in callers skip Turnstile and get recorded as submitter, anonymous callers must supply organizer_email. It gives strong when/how conditions but does not name alternative tools or explicit exclusions.

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