parse_to_vault

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states the tool writes markdown to the vault, includes audit trail in frontmatter, and matches the output shape of the script. It does not contradict any annotations (none exist) and adds meaningful context about the output format and the router integration, though it does not cover error handling or side effects beyond what the schema already implies.

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 two sentences with no waste. The primary purpose is stated first, followed by the replacement context and key behavioral difference. It is front-loaded and efficient, making it easy for an agent to parse quickly.

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 presence of an output schema and full parameter schema descriptions, the description provides sufficient overarching context: what it does, where it writes, and what the output contains. It could mention prerequisites (e.g., file accessibility) or failure modes, but these are secondary given the schema details. Overall it is fairly complete for an agent to call correctly.

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 input schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The tool description adds no additional meaning about specific parameters, only an overall behavioral context (e.g., audit trail in frontmatter) that indirectly relates to the 'backend' parameter but does not explain how to use it. Since the schema already documents each parameter clearly, this is appropriate.

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 states a clear, specific action ('Parse a document and write it to the vault as a markdown note') with a specific resource and destination. It further distinguishes the tool by noting it replaces a standalone script and adds an audit trail, so an agent can tell it apart from generic parse tools like 'parse' or 'interpret'.

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 implies the primary use case (persisting parsed output to the vault) and explicitly references the replacement of a shell script, which gives context. However, it does not explicitly compare with sibling tools like 'parse' or 'parse_url' or state when to prefer this over them. The guidance is present but not fully explicit.

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