nworks_calendar_delete

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

With no annotations provided, the description carries the full burden and successfully discloses OAuth scope requirements (calendar + calendar.read). However, it lacks disclosure about whether deletion is permanent versus reversible, idempotency behavior, or what the tool returns upon success/failure.

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?

Four sentences with zero waste: action definition, usage scenario, authentication requirements, and prerequisite workflow. Information is front-loaded and every sentence earns its place.

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 3-parameter deletion tool with no output schema, the description adequately covers the operation's purpose, prerequisite workflow, and security constraints. Minor gap in not describing return values or error conditions, but sufficient for safe invocation.

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?

While the input schema has 100% description coverage (establishing a baseline of 3), the description adds valuable OAuth authentication context not present in the schema, providing necessary behavioral constraints for the userId parameter usage.

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 the specific action '캘린더 일정을 삭제합니다' (deletes calendar events) and distinguishes itself from siblings like nworks_calendar_create, nworks_calendar_list, and nworks_calendar_update through the explicit deletion verb.

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?

Explicitly identifies when to use the tool ('일정 취소해줘' 등의 요청에 사용 for cancellation requests), references the prerequisite tool for obtaining required parameters (eventId는 nworks_calendar_list로 조회 가능), and states authentication requirements (User OAuth 인증 필요).

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