discord_edit_scheduled_event

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Edit a scheduled event' and 'fields = raw Discord event fields' without explaining effects (e.g., whether editing a started event is allowed, if changes are immediate, or if there are any rate limits or side effects).

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 very short (two sentences) and front-loaded with the core action, but it is arguably too terse. While concise, it sacrifices informativeness; every sentence could earn its place with more detail about the 'fields' parameter or usage context.

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 complexity (3 required parameters, one nested object, no output schema), the description is insufficient. It lacks details on what fields are editable, the structure of the 'fields' object, expected response, and error conditions. The description is incomplete for effective use.

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 0%, yet the description only adds meaning for the 'fields' parameter ('raw Discord event fields'), which is vague. It does not explain 'guildId' or 'eventId' beyond their names, leaving the agent to infer their purpose. The description adds minimal value beyond the schema.

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 action 'Edit' and the resource 'scheduled event', making the tool's purpose immediately understandable. However, it does not differentiate from sibling tools like discord_create_scheduled_event or discord_delete_scheduled_event, missing an opportunity to clarify scope.

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 guidance is provided on when to use this tool versus alternatives (e.g., when to edit vs create or delete). There is no mention of prerequisites, such as needing the bot to have manage events permission or the event being in a specific state.

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