obsidian_toggle_task

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

With no annotations, the description carries the full behavioral burden. It states the operation is a mutation ('Toggles') and mentions 'verification', but does not say what happens when expectedText/expectedRevision mismatch, whether the change is reversible, or what permissions are needed. The verification hint is the only real behavioral disclosure.

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?

A single efficient sentence with the action front-loaded and no filler. It is well-sized, though the trailing 'with verification' clause is vague rather than informative.

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 4-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description is under-specified. It omits the meaning of the verification parameters, failure behavior, and any return information an agent would need to call it confidently.

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 description coverage is 0% across 4 parameters. The description implies 'path' (a note) and 'line' but never explains the semantics of expectedText or expectedRevision, nor why 'line' is 1-based. It does not compensate for the total lack of schema documentation.

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 names a specific verb ('Toggles') and resource ('completion checkbox on a specific line of a note'), making the action clear and distinct from siblings like obsidian_update_note or obsidian_list_tasks. It does not explicitly differentiate itself from those siblings, but the toggling action is unambiguous.

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?

There is no guidance on when to use this versus alternatives such as obsidian_update_note or obsidian_list_tasks, nor any statement of prerequisites. 'with verification' hints at a precondition but is never explained as a when-to-use rule.

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