doc_import

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

With no annotations, the description carries the full burden. It does disclose that the tool automatically uploads the file and converts to docx, and implies that without space_id, a subsequent wiki_move_docs_to_wiki call would be needed. However, it lacks details on permissions, default folder behavior, return values, or error conditions, which are expected for a creation/upload tool.

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 a single, well-structured sentence that front-loads the primary purpose, then adds the optional usage in a dependent clause. Every word contributes, with no redundancy or filler.

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 moderate complexity (5 params, 1 required, no output schema), the description covers the main use case, the wiki shortcut, and a key behavioral trait. It does not explain the default destination when neither space_id nor folder_token is provided, nor does it describe the return value, but it is generally sufficient for an agent to select and invoke the tool correctly in most scenarios.

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 the baseline is 3. The description adds value by explaining that space_id and parent_wiki_token work together to write directly into the wiki, and that file_name relates to the docx filename. This contextualizes the parameters beyond their individual 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 action: importing Markdown content to create a Feishu document, with the specific behavioral detail of automatically uploading and converting to docx. It also distinguishes itself from the sibling wiki_move_docs_to_wiki by noting the direct wiki integration saves a manual step, making the tool's purpose unambiguous.

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 explicit usage guidance by mentioning the optional space_id + parent_wiki_token to directly write to the knowledge base, and explicitly says this saves the need to manually call wiki_move_docs_to_wiki. This gives clear when-to-use context, though it does not discuss alternatives like wiki_create_node_with_markdown.

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