Complete a task

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

No annotations are provided, and the description discloses no behavioral traits: no mention of side effects, whether the task must exist, whether sessions are affected, or reversibility. For a mutating operation, this is a significant omission.

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 extremely short and front-loaded, but it is under-specified rather than appropriately concise. A single sentence provides almost no useful information beyond the title.

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 simple one-parameter tool, the description is minimal but still incomplete: there is no output schema, so the agent does not know what the tool returns, and no error or edge-case behavior is mentioned. Given the lack of annotations, the description carries the full burden and fails to cover it.

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 only parameter, task_id, has zero schema description coverage (0%). The description does not mention it or clarify its meaning beyond the name. The agent must infer that task_id identifies the task to complete, leaving no added value.

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 'Mark a task as completed' states a clear verb and resource, and it is distinguishable from siblings like dwt_create_task or dwt_list_tasks. However, it essentially restates the tool name and title, adding little new information.

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 is given on when to use this tool versus alternatives such as dwt_switch_task or dwt_start_session. The intended use case is only implied by the name, and no exclusions or conditions are mentioned.

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