obsidian_create_task

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

The description discloses non-obvious behaviors: semantic fields are passed to obsidian-writer for final Markdown formatting, and dependencies are accepted but not sent. This goes beyond a simple 'create task'. However, it does not describe return values, failure modes, or vault prerequisites.

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 four concise sentences with purpose first, usage guidance second, and technical caveats last. No redundant or filler content.

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?

With 15 parameters, no annotations, and no schema descriptions, the description is too sparse to fully guide invocation. It omits parameter meanings, date formats, vault targeting, and expected output, making it incomplete for correct usage.

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 schema has 0% description coverage and the description does not explain individual parameters. It only generalizes that semantic fields should be passed and notes depends_on is ignored, leaving 14 other parameters unspecified.

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 first sentence clearly states 'Create a structured Obsidian Tasks-compatible task in a vault', specifying the verb, resource, and format. This distinguishes it from sibling tools like obsidian_create_note and obsidian_list_tasks.

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?

The description explicitly states when to use it: 'Use when the user asks for a task, todo, manual reminder, or pending action.' It provides clear trigger conditions, though it does not mention alternatives or exclusion cases.

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