export_events

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description adds meaningful behavior beyond that: it normalizes and exports partial event data into an ICS-oriented shape. It does not go into return format or idempotency, but the annotations reduce the burden and the 'normalize/export' description gives a clear sense of the operation.

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 compact and front-loaded: it states the purpose first, then the endpoint, then the parameter shape, then the trigger condition. Every sentence contributes useful information and there is no filler.

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 one-parameter tool with annotations already covering safety, the description covers purpose, usage, and basic parameter semantics. However, it does not explain the return/result of the export or clarify the JSON-encoding issue between the string schema and the described array, leaving an important operational gap.

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%, so the description must compensate. It does add some value by listing the kinds of fields (id/start/end/summary) and calling the value an array of partial events, but it conflicts with the schema, which declares events_json as a string, and the POST example uses 'events:[...]' rather than 'events_json'. This ambiguity could mislead an agent about how to serialize the parameter.

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 uses a specific verb ('normalize/export') and identifies the resource ('partial event objects') with a distinct shape ('ICS-oriented shape'). It is clearly differentiated from sibling tools like get_events, search_events, and create_event, since none of them are described as export/normalization operations.

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 states when to call the tool: 'Call when packaging events for export.' It provides clear context for the intended use case, though it does not explicitly discuss when not to use it or name an alternative tool.

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