create_from_markdown

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

With no annotations, description carries burden; it discloses automatic opening and smart typography application. However, it lacks detail on error handling, overwrite behavior, and required permissions.

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?

Well-structured: summary, markdown support details, usage constraint, then parameter list. Front-loaded with purpose. No redundant sentences.

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?

Moderate complexity with 5 parameters and mutual exclusivity; description adequately covers inputs and behavior. Output schema exists, so return values not needed. Lacks error scenarios but sufficient for common use.

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 0%, so description adds value by explaining each parameter: output_path, md_path, markdown, template_path, document_handle. It clarifies mutual exclusivity and optionality. Could improve with format constraints.

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 creates a .docx document from markdown content, with specific verb and resource. It distinguishes from siblings like 'create_document' and 'export_markdown' by mentioning markdown input and document creation.

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 states 'Provide exactly one of md_path or markdown', clarifying mutual exclusivity. It mentions automatic opening for editing. Does not explicitly contrast with 'create_document' but context is clear.

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