nworks_task_delete

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

No annotations provided, so description carries full disclosure burden. It successfully discloses authentication requirements ('User OAuth 인증 필요 (task + user.read scope)'), but omits mutation consequences such as whether deletion is permanent, recoverable, or if there are cascading effects on related data.

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?

Three sentences, each serving distinct purposes: (1) action definition, (2) prerequisite lookup, (3) authentication requirements. No redundancy or filler. Front-loaded with the core action. Excellent information density for the complexity level.

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 single-parameter deletion tool with no output schema, the description adequately covers the operational essentials: action, parameter acquisition, and auth. Could be improved by noting if deletion is permanent or reversible, but sufficient for basic invocation given the simple schema structure.

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 coverage is 100%, with the schema fully documenting the taskId parameter including its source. The description repeats the taskId sourcing information but adds no additional semantic context (formats, constraints, examples) beyond what the schema already provides. Baseline 3 is appropriate given comprehensive schema coverage.

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?

Description clearly states '할 일을 삭제합니다' (Deletes a task) with specific verb and resource. The mention of taskId sourcing from nworks_task_list effectively distinguishes this from sibling task tools (create, update, list), though it could briefly clarify what constitutes a 'task' in this system.

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 prerequisite guidance: 'taskId는 nworks_task_list로 조회 가능' (taskId can be queried via nworks_task_list), directing users to a specific sibling tool. Also discloses OAuth authentication requirements. Lacks explicit 'when not to use' guidance, but covers the essential prerequisite chain.

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