update_event

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

With no annotations provided, the description carries the full burden. It discloses the tool's limited scope (only changes timestart) and warns that full event updates are unavailable, which is key behavioral context. However, it does not mention permissions, return values, or side effects on existing event details, which would have strengthened transparency further.

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 two focused sentences, with the primary action front-loaded. The second sentence efficiently conveys the limitation and alternative without redundancy, making every word count.

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 simple two-parameter mutation tool, the description covers the core behavior, its limitation, and the recommended alternative for other changes. No output schema exists, but the tool's purpose is fully explained, making it complete for an agent to decide when and how to invoke 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 50% (only new_timestart has a description). The description implies the role of event_id (which event) and new_timestart (the new time), but it adds little beyond what the schema already states. It does not elaborate on event_id's format or any constraints 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 tool reschedules a calendar event to a new timestart, using a specific verb and resource. It also distinguishes itself from siblings by explicitly noting that other changes (name, description, location) are not supported, setting it apart from create/delete event tools.

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 explicitly says when to use this tool (to reschedule) and when not to (to change name/description/location), providing the alternative of delete + re-create. This is a clear usage guideline with an explicit exclusion, referencing the Moodle WS limitation.

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