Export Vault

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

Annotations already indicate non-destructive and idempotent behavior. The description adds valuable detail that goes beyond annotations: it copies original files rather than extracted text, and exports all documents. It does not mention overwrite behavior or directory creation, but the annotation profile reduces the need for more.

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 three concise sentences: it states the action, clarifies the copy behavior, and indicates a use case. It is front-loaded with the essential purpose and contains no fluff or redundancy.

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?

The tool is simple (two parameters) and has an output schema, so return values are already covered. The description covers the core functionality, the type of data copied, and typical use cases. It could mention whether the directory must pre-exist or if structures are preserved, but overall it is sufficient for an agent to invoke 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?

With schema description coverage at 0%, the description must compensate. It implicitly maps parameters by saying 'from a vault to a local directory,' which clarifies vault and directory roles. However, it does not define parameter formats, accepted values, or path conventions, leaving a gap that a more detailed description could fill.

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 a specific verb and resource: 'Export all documents from a vault to a local directory.' It distinguishes from siblings like vault_export_manifest by specifying 'Copies the original files (not extracted text)' and 'all documents,' which separates it from manifest or single-doc export tools.

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?

It provides clear context for when to use the tool: 'Useful for backing up or sharing vault contents.' However, it does not explicitly exclude alternatives or mention when not to use it, such as when only a manifest is needed (vault_export_manifest). This is a clear context without exclusions.

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