obsidian_uncomplete_task

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

No annotations present, and the description fails to disclose behavioral traits like in-place note modification, permission requirements, or side effects. The return type is vaguely described as 'Success message or error'.

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?

Extremely concise but at the cost of missing critical details about behavior and parameters. The format is front-loaded but under-specified.

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?

Lacks context for a mutation tool with three required parameters and no schema descriptions. Does not explain edge cases, error conditions, or the exact effect of the operation.

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?

With 0% schema description coverage, the description adds no semantics beyond parameter names. It does not clarify how task_description_contains matches (e.g., exact, substring) or path formatting.

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?

Clear verb-resource combination: 'Mark a completed task as incomplete.' It directly contrasts with sibling tools like obsidian_complete_task, which performs the opposite action.

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 on when to use this tool versus alternatives such as obsidian_update_task or obsidian_delete_task. No when-not-to-use or prerequisite information provided.

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