obsidian_save_memory

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool saves a voice memory but does not mention idempotency, overwrite behavior, storage details, or any side effects. This is insufficient for a write 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 a single, front-loaded sentence that immediately conveys the trigger and action. It is concise with no fluff, though it sacrifices necessary detail for brevity.

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 2 parameters, no output schema, no annotations, and 0% schema coverage, the description is critically incomplete. It fails to explain expected input format, return behavior, error handling, or storage semantics, leaving the agent without essential context.

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%, and the description does not explain the parameters ('text' and 'tags'). The default value for 'tags' is given in the schema but its purpose is not clarified. The description adds no meaning beyond the schema.

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 specifies when to call ('当用户说记一下/保存想法/写到 Obsidian时调用') and what it does ('保存一条语音记忆'). It clearly indicates the verb (save) and resource (voice memory), and distinguishes from sibling tools like obsidian_create_note by focusing on memory rather than general notes.

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 includes a usage trigger phrase ('当用户说...时调用'), giving explicit context for when to invoke. However, it lacks guidance on when not to use or alternatives among siblings (e.g., obsidian_create_note for structured notes).

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