archimate_create_model

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

With no annotations provided, the description carries the full burden. It discloses that the model is empty and includes a standard folder structure, but does not explain side effects (e.g., whether it saves automatically, overwrites existing files) or required application state.

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 clear sentence with no unnecessary words. While concise, it could include additional brief context without becoming verbose. It is appropriately front-loaded but just a touch lean.

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, the description does not mention return value (e.g., model ID or success indication). For a create tool with two simple parameters, the description is adequate but could be more complete by hinting at next steps (e.g., 'Use this before adding elements or views').

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 baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions ('Name of the new model', 'Path where to save the model'), only incrementing the context of 'standard folder structure'.

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 ('Create a new empty ArchiMate model') and the resource ('with standard folder structure'), distinguishing it from sibling tools like archimate_create_view (creates a view within a model) and element creation tools.

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 starting a new model but does not explicitly state when to use this tool versus alternatives like opening an existing model (archimate_open_model) or creating views/elements. No exclusions or prerequisites are mentioned.

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