Create Scheduled Event

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

Annotations indicate it's not read-only (readOnlyHint=false) and may have open-world side effects. The description discloses it creates an event but does not elaborate on permissions, rate limits, or failure behavior.

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 long due to parameter listing, but it is structured with Args and Returns sections. It front-loads the main action. However, it repeats schema information which could be more concise.

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?

No output schema given, the description mentions 'Created event details' but not fields. There is inconsistency: description lists 'location' as a separate parameter, but schema nests it inside 'entity_metadata'. Does not explain that scheduled_end_time is required for external events (schema mentions it).

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 description adds limited new meaning. It lists parameters with types and optionality, but essentially repeats schema info. Minor added value in clarifying entity_type enum and location field.

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 'Create a scheduled event in a server', specifying the action and resource. It distinguishes from sibling tools like discord_list_events (read) and discord_delete_event (delete).

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?

No explicit guidance on when to use this tool versus alternatives. No mention of prerequisites like required permissions or when not to use it.

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