calendar_update_event

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

Discloses partial update behavior and timezone interpretation. With no annotations, description carries full burden; missing details on idempotency, error handling, 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?

Three concise sentences with key points front-loaded. No unnecessary fluff.

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?

Covers main points (confirm, partial update, timezone) but lacks output specification, error cases, and permissions. For an 8-param tool with no output schema, more detail is warranted.

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 only 38%, but description adds little beyond 'Only provided fields are changed' and repeats 'confirm=true'. Does not explain un-described parameters like event_id, calendar_id, title, etc.

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?

Clearly states 'Update an existing Synology Calendar event' with specific verb and resource. Distinguishes from sibling tools like create, delete, get.

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?

Mentions 'Requires confirm=true' and 'Only provided fields are changed', which provide context for usage. Does not explicitly state when not to use vs alternatives, but sibling tools are distinct.

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