obsidian_add_task

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

No annotations are provided, so the description carries full burden. It only states returns 'Success message or error' but fails to disclose whether the task is appended to the note, if it creates a checkbox, or if it is idempotent. Critical behavioral details are missing.

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 highly concise with a single-sentence purpose, a clean list of parameters with types/behaviors, and a returns line. Every sentence is necessary, and no words are wasted.

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?

Given the complexity (7 params) and many sibling tools, the description is incomplete. It does not explain how the task is added (e.g., appended, inserted at cursor), the format of the task, or how it interacts with the note content. No output schema exists, yet the return value is vaguely described.

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 0%, so description must compensate. The docstring provides brief but clear descriptions for all parameters (e.g., due_date format, priority options, tags as comma-separated), adding meaning beyond the schema's titles.

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 action 'Add a new task to a note' with a specific verb and resource. It distinguishes itself from sibling tools like obsidian_complete_task, obsidian_delete_task, and obsidian_update_task by focusing on creation.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it differs from similar tools like obsidian_create_note or obsidian_update_task.

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