mcp-markdown-vault

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It lists actions but doesn't describe their effects (e.g., whether 'delete' is permanent, if 'create' requires specific permissions, or how errors are handled). For a tool with multiple mutating actions (create, update, delete), this is a significant gap in transparency about risks and outcomes.

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 concise and front-loaded, stating the core purpose in the first clause. It uses two sentences efficiently: one for actions and one for context. There's no wasted verbiage, though it could be slightly more structured (e.g., bullet points for actions) for a perfect score.

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 tool's complexity (6 parameters, multiple actions including mutations), lack of annotations, no output schema, and low schema description coverage (33%), the description is insufficient. It doesn't address behavioral traits, parameter details beyond actions, or output expectations, leaving critical gaps for safe and effective use by an AI agent.

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 description mentions actions but doesn't explain parameters beyond what the schema provides. Schema description coverage is 33% (only 'templatePath' and 'variables' have descriptions), leaving most parameters undocumented. The description adds minimal value by hinting at action types but doesn't compensate for the low coverage with details on usage, formats, or constraints for parameters like 'path', 'directory', or 'content'.

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 tool's purpose: 'Manage vault notes: list, read, create, update, delete, stat, create_from_template.' It specifies the verb ('manage') and resource ('vault notes'), and adds context about operating on '.md files in the markdown vault.' However, it doesn't explicitly distinguish this tool from its siblings (edit, system, view, workflow), which would be needed for a score of 5.

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 guidance on when to use this tool versus its siblings (edit, system, view, workflow). It mentions the actions available but doesn't specify contexts, prerequisites, or alternatives. This lack of comparative guidance limits the agent's ability to choose appropriately among available tools.

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