create-calendar-event

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

Annotations indicate 'destructiveHint: true', but the description focuses on extended properties rather than calendar event creation, which contradicts the tool's apparent purpose. The description does not disclose behavioral traits beyond the annotations, and the mismatch undermines transparency.

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 relatively short but includes irrelevant content about extended properties and a tip that, while helpful, does not align with the tool's schema. The structure is not optimized for clarity.

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 the tool's complexity (many nested parameters, no output schema), the description is insufficient. It does not explain the return behavior, authentication needs, or how the tool interacts with calendar resources. The tip is useful but not comprehensive.

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?

The input schema has 67% description coverage, and the description adds no additional meaning to the parameters. It fails to explain how to use the complex nested objects (e.g., attendees, recurrence) beyond what the schema already provides.

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 states 'Create one or more multi-value extended properties in a new or existing instance of a resource,' which is mismatched with the tool name 'create-calendar-event' and the input schema that defines a calendar event structure. This creates confusion about the tool's actual function. The description does not effectively differentiate from sibling tools like 'create-specific-calendar-event'.

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 tip about using 'list-users' to find email addresses provides some usage guidance. However, there is no explicit instruction on when to use this tool versus alternatives (e.g., 'create-specific-calendar-event') or any prerequisites or context for invoking the tool.

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