obsidian_delete_property

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

No annotations are provided, so the description must carry the burden. It only states it returns a success message or error, but does not disclose behavior if the property doesn't exist, if the note doesn't exist, or whether the action is idempotent. This is insufficient for a destructive operation.

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 concise with a one-line purpose, a structured list of arguments, and a return type. Every sentence is necessary and no space is 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 that the tool has only three required parameters and an output schema exists, the description covers the basic operation. However, it lacks details on edge cases (e.g., behavior when property is missing) and context on when to choose this over related tools like obsidian_set_property.

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%, but the description adds minimal value beyond the parameter names. It repeats 'vault', 'path', and 'property_name' with a brief explanation that property_name is the name to delete. No format, constraints, or examples are given, leaving the agent to infer.

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 verb 'delete' and the resource 'frontmatter property from a note', distinguishing it from sibling tools like obsidian_set_property or obsidian_get_properties.

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 explicit when-to-use or when-not-to-use guidance is provided. The usage is implied by the simple destructive nature, but for an AI agent, more context on prerequisites or alternatives (e.g., when to use obsidian_set_property instead) would be beneficial.

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