discord_get_scheduled_event

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

Annotations already declare readOnlyHint=true, so transparency is partially covered. The description adds that it is read-only and returns a JSON object, but does not disclose additional behavioral traits like error handling, rate limits, or permission requirements beyond the schema.

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: first states purpose and lists returned fields, second states read-only nature and return type. No unnecessary words, front-loaded with key 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?

Given the tool's simplicity, the description adequately covers the purpose and return format. The presence of an output schema compensates for not detailing the exact return structure. However, could mention that the event must exist or that guild_id and event_id are required (already in schema).

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% and describes both parameters (event_id, guild_id) with patterns. The description does not add extra meaning or usage details for the parameters beyond what the schema provides.

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 tool gets full details for one scheduled event, listing specific fields (name, description, status, etc.). It distinguishes from sibling tools like discord_list_scheduled_events, which lists events, and create/edit/delete variants.

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 description implies usage for fetching a single event's details, but does not explicitly mention when to use this tool vs alternatives (e.g., discord_list_scheduled_events for listing, discord_get_event_subscribers for subscribers). No when-not-to-use guidance.

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