discord_get_scheduled_event

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' mostly restates structured data. The list of returned fields adds some value, but it largely duplicates the output schema that already exists; nothing about permissions, rate limits, or failure behavior is added.

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 short sentences, front-loaded with purpose and the returned fields, with zero filler. Every clause carries 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 an output schema present and full parameter coverage, the description only needs purpose and safety framing, both of which it supplies. The one gap is guidance on when to fetch a single event versus listing events, which happens at the usage-guideline level.

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 100% with both guild_id and event_id documented as snowflake IDs, so the description's job here is minimal. It adds no syntax or format detail beyond the schema, which is the appropriate baseline.

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 (Get) plus resource (scheduled event) and an explicit scope of 'one', with the returned fields enumerated. An agent can tell it apart from discord_list_scheduled_events (plural list) and discord_get_event_subscribers without opening a schema.

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 'for one scheduled event' establishes the context: use this when you already have a specific event rather than enumerating events. It never explicitly rules out or names the alternative (discord_list_scheduled_events) for discovery, so it stops short of a 5.

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