promote_document

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

Discloses auto-detection of project, fallback to inbox, and copy vs move behavior. No annotations exist, so description carries full burden. It provides sufficient transparency beyond simple mutation.

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?

Four succinct sentences: purpose, usage, auto-detection, copy/move default. Front-loaded with no redundant information.

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?

Covers key behaviors and parameters. Lacks output specification, but for a simple import tool this is acceptable. Could hint at return value (e.g., confirmation path).

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 coverage is 100% but description adds meaning: copy default true, project auto-detected, source absolute path. Each parameter gets extra context beyond schema descriptions.

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: 'Promote a document from an external vault (e.g. Obsidian) into the alcove doc-repo.' This distinguishes it from sibling tools like get_doc_file or search_vault, which deal with internal documents.

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?

Explicitly says 'Use this tool when the user wants to import, migrate, or copy a file from outside alcove.' Provides context but does not explicitly list when not to use or alternative tools.

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