create_event

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

No annotations are provided, so the description carries the full burden. It usefully reveals that the event is created in draft state and that timestamps must be UTC strings in a specific format. It does not mention permission requirements, side effects, or how defaults apply to omitted parameters.

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 only two sentences, with the core action front-loaded and the timestamp constraint placed immediately after. There is no filler or redundant 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?

For a 12-parameter creation tool with no annotations and no schema descriptions, this is thinly documented. The description covers draft state and timestamp encoding, but does not explain key optional parameters or relationships like venue_id referencing an existing venue; the output schema does not compensate for missing parameter semantics.

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 description coverage is 0%, so the description must compensate. It only clarifies the timestamp format and organizational scope; the meanings of parameters like listed, shareable, online_event, capacity, and venue_id are left entirely to inference from names and defaults.

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 states a specific verb and object: it creates a new draft event under an organization. This clearly distinguishes it from update_event, publish_event, and copy_event, and the word 'draft' makes the resulting state explicit.

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?

The phrase 'new draft event' implies this is for first-time event creation rather than editing or publishing. However, there is no explicit guidance on when to prefer this over alternatives like create_event_schedule or update_event, nor any conditions that would exclude it.

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