Create custom event (admin)

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

Discloses mutation ('MUTATES live game config') beyond annotations, which already indicate not read-only and not idempotent. Adds user confirmation and staging preference. No contradictions with annotations.

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?

Two sentences plus a warning, all earning their place. Front-loaded with purpose and example.

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?

Adequate for a tool with 6 parameters and no output schema: covers purpose, ordering, and mutation. Lacks detail on fields and parameters, but sufficient for basic usage.

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 50% schema coverage, description adds value by explaining eventId auto-derivation from name and giving an example for parameters. However, fields and projectId remain unexplained, and compensation is not full.

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 clearly states the verb ('Create'), resource ('custom event'), and purpose ('that tasks/achievements can be triggered by'), with an example. It distinguishes from sibling create_* tools by focusing on events.

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?

Provides explicit ordering advice: 'Create the event BEFORE the task that references it' and cautions to 'confirm with the user and prefer staging' due to mutation. No explicit alternatives mentioned, but context is clear.

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