createCalendar

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

No annotations provided, so description must cover behavior. It only mentions API version and parameter conditions. Does not disclose if it overwrites, validates leadId, or returns an ID. Minimal transparency beyond creation action.

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, no redundancy. First sentence states purpose and API version, second gives conditional guidance. Highly concise.

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?

No output schema, so description should mention return value (e.g., created item ID). Does not clarify time specification (startAt/endAt vs startAtMs/endAtMs). Incomplete for agent to properly use tool.

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 has 100% coverage, but description adds conditional meaning: 'For TASK provide taskWay and assignedRole; for APPOINTMENT provide address.' This clarifies which optional parameters are relevant for each type, beyond the required list.

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?

Clearly states 'Create a calendar item (v2 API)' and distinguishes between TASK and APPOINTMENT types. The verb 'create' and resource 'calendar item' are specific. Differentiates from siblings like updateCalendar or listAppointments.

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?

Provides explicit guidance for when to use TASK vs APPOINTMENT, including required parameters for each. Could mention when to use updateCalendar instead, but the conditional instruction is clear.

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