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 mentions 'manage the server' which implies potential mutations, but doesn't clarify permissions, side effects, or response formats. This is inadequate for a tool with administrative functions.

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, listing key functions in a single sentence. However, 'manage the server' is vague and could be more specific to improve clarity without adding length.

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 administrative complexity, lack of annotations, and no output schema, the description is insufficient. It omits critical details like authentication needs, mutation risks, and return values, leaving significant gaps for agent understanding.

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 50%, with the 'action' parameter documented via enum and 'maxDepth' having a description. The description adds no parameter-specific semantics beyond what the schema provides, but the schema covers half the parameters adequately, meeting the baseline.

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 as 'System administration' with specific functions: 'check status, get indexing info, vault structure overview, and manage the server.' It uses concrete verbs and resources, though it doesn't explicitly differentiate from sibling tools like 'vault' or 'workflow'.

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 alternatives. It lists functions but doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer usage from the action parameter alone.

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