create_event

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

No annotations are provided, so the description must carry the full burden. It only states the action ('create'), implying mutation, but lacks details on idempotency, error behavior, permissions, or data validation. The format of event_json is vaguely described but not constrained.

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?

Two sentences with the primary purpose first and parameter explanation second. Efficient and front-loaded, no fluff. Could be slightly more detailed without sacrificing 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?

Despite having an output schema, the tool is a creation operation with a single complex JSON parameter. The description does not explain the event's required properties, validation rules, or side effects. Given the low schema coverage and no annotations, it is incomplete for an agent to use correctly.

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%. The description adds minimal value: '`event_json` is a JSON object string.' This tells the type but not required fields, format, or examples. The agent cannot infer the structure of the JSON object.

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 'Create a new calendar event,' specifying the verb and resource. It distinguishes from sibling tools like create_account or create_contact by focusing on calendar events. However, it lacks specificity about the calendar system (e.g., Google Calendar vs. internal).

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?

No guidance on when to use this tool versus alternatives like find_events or hypothetical update_event. No exclusions or prerequisites mentioned. The agent is left without context for appropriate invocation.

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