Create All-Day Event

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

Annotations only provide a title; no readOnlyHint or destructiveHint. The description 'Create' indicates mutation but lacks information on permissions, reversibility, or side effects. Output schema exists but its content is unknown.

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 a single short sentence, which is concise, but it sacrifices essential detail. It could be expanded with key parameter info without losing conciseness.

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 6 parameters (2 required) and no schema descriptions, the description is insufficient for complete understanding. The output schema exists but its content is not conveyed. Sibling tools are numerous but differentiation is minimal.

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%, and the description provides no explanation for any of the 6 parameters (e.g., date format, purpose of url, notes, location, calendar_uid). Agents must rely solely on parameter names.

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 'Create an all-day event for one local date' clearly states the verb (Create), resource (all-day event), and scope (one local date). It distinguishes from the sibling 'calendar_create_event' which likely handles timed events.

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 implies usage for day-specific events but does not explicitly state when to use this tool over alternatives like 'calendar_create_event'. No when-not or alternative guidance is provided.

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