archimate_create_composite_element

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the tool creates an element, but does not describe side effects, required permissions, return behavior, or whether it modifies an existing model. This is insufficient for an agent to understand the tool's impact.

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 very short, consisting of one sentence and a short clause. It front-loads the core action ('Create a composite element'). However, the parenthetical '(Chapter 4)' is cryptic and does not earn its place, slightly reducing 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?

The tool has 3 parameters, no output schema, and no annotations. The description does not explain return values, whether the model must be open, or how to interpret the result. Given the complexity of creating an element and the many sibling tools, the description is too minimal to be fully complete.

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?

The input schema has 100% description coverage and includes detailed descriptions for each parameter (e.g., element_type explains 'Grouping (aggregate concepts), Location (place where things are located)'). The tool description reinforces this with 'Use for grouping and locations', adding context beyond the schema. According to guidelines, high schema coverage yields a baseline of 3, but the description adds meaningful value, justifying a 4.

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 states 'Create a composite element (Chapter 4). Use for grouping and locations.' It identifies the verb (Create) and resource (composite element) and mentions the two enum types (Grouping, Location). However, it does not clearly differentiate from sibling element creation tools (e.g., archimate_create_application_element) beyond the enum values, and the 'Chapter 4' reference is obscure.

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 phrase 'Use for grouping and locations' gives some context for when to use this tool (creating Grouping or Location elements). However, it provides no explicit guidance on when not to use it or alternatives among the many sibling tools for creating other element types.

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