Create event

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only 'with ICS data' and says nothing about permissions, what calendar_url must point to, or how idempotency keys are derived from event_data/filename.

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 single sentence is front-loaded and has no wasted words. It is too terse rather than rambling, but the structure is at least clean and easy to parse.

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 write tool with three parameters at 0% schema description coverage and no output schema, the description should clarify the ICS string format, the calendar_url target, and the filename default. None of that is present, leaving the agent to guess at call shape.

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 0%, so the description must explain the three parameters. It only hints that `event_data` is ICS data and leaves `calendar_url` and `filename` completely undefined, including whether `filename` is derived from the event UID or controls storage naming.

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?

States a specific verb and resource ('Create an event') and adds the notable detail that the payload is ICS data. However, it does not distinguish itself from the sibling tool `nextcloud_create_calendar_event`, so an agent cannot tell which creation tool is correct without opening both schemas.

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?

There is no guidance on when to use this tool versus `nextcloud_create_calendar_event` or the other create_* siblings. Usage is only implied by the tool name and the word 'event'.

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