archimate_export_html_deck

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

No annotations are provided, so the description bears the full burden. It states the tool exports a model, suggesting a read-only operation, but doesn't disclose potential side effects, performance constraints, or prerequisites. The minimal disclosure limits transparency but doesn't mislead.

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, efficient sentence that conveys the core functionality without verbose or redundant content. Every word contributes to the purpose, achieving high conciseness.

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 lack of output schema and annotations, the description should cover prerequisites (e.g., model must be open) and output behavior (e.g., file size). It does not address these, leaving the agent with insufficient context for a 5-parameter tool.

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. The description adds no extra parameter meaning beyond what the schema already provides (e.g., 'output_path', 'theme'). It does not elaborate on parameter usage or formatting, so no added value.

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 verb 'Export' and the resource 'model as an interactive HTML deck with tabs and search'. This distinguishes it from sibling tools like 'archimate_export_diagram' (single diagram) and 'archimate_export_markdown' (text), making the 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 implies usage: when an interactive HTML deck is needed. However, it doesn't explicitly contrast with siblings nor state when not to use. The sibling names provide implicit context, but direct guidance is missing, earning a 4 for clear but non-exclusive context.

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