archimate_export_markdown

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

With no annotations provided, the description carries the full burden of disclosure. It only states the action (export) and format (Markdown) without mentioning side effects, safety behavior (read-only or mutation), file system implications, or output characteristics. Critical behavioral context is missing.

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 6-word sentence, which is highly concise and front-loaded. However, for a tool with 5 parameters and many siblings, it might be slightly too sparse, but it avoids any unnecessary text.

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 complexity (5 parameters, no output schema, no annotations) and the presence of multiple sibling export tools, the description is insufficient. It does not clarify the output structure, how it differs from other Markdown-like exports, or that it requires a file path. The tool's role in the workflow is underdescribed.

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 100%, so the baseline is 3. The description does not add any extra meaning beyond what the schema already provides for each parameter. It merely lists the action without enriching parameter semantics.

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 'Export the model as Markdown documentation,' using a specific verb and resource. It distinguishes itself from sibling export tools (e.g., archimate_export_diagram, archimate_export_exchange, archimate_export_mermaid, archimate_export_html_deck) by specifying the output format.

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 no guidance on when to use this tool versus the many sibling export tools (e.g., archimate_export_mermaid, archimate_export_html_deck). No context about scenarios, prerequisites, or exclusions is given.

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