Import Document

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

Annotations already mark it as readOnly and idempotent. Description adds key behavioral info: converts to Markdown, returns content/metadata/word count, and crucially notes that compressed Office/PDF files fail with an actionable error. No contradiction with annotations.

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?

Description is well-structured with front-loaded main action and subsequent details. Every sentence adds value. Slightly long due to full format list and error advice, but efficient overall.

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 no output schema, description covers all needed context: what it does, return values (content, metadata, word count), format support nuances, and failure handling. Complete for a read-only import tool with multiple file types.

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% so baseline is 3. Description adds significant meaning beyond schema: explains format support levels ('fully supported' vs. 'fail'), clarifies error behavior for compressed files, and connects raw_text and file_path usage. This justifies a 4.

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?

Description clearly states verb (import document), resource (document formats and raw text), and outcome (converts to Markdown for SDD processing). Distinguishes from siblings like sdd_batch_import and sdd_import_transcript by focusing on single document import and conversion.

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?

Provides explicit context on when to use (for importing and converting documents) and notes limitations (compressed Office/PDF fail) with workarounds (install MarkItDown or convert). However, does not explicitly contrast with sibling import tools like sdd_batch_import.

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