archimate_add_to_view

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

Without annotations, the description bears full burden. It discloses auto-connection behavior and response content (autoConnectedRelationships). It does not mention potential side effects like duplicate adds, but the behavior is adequately described for a view mutation tool.

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?

Two sentences, no filler. The action and key behavior are front-loaded. Every sentence serves a purpose.

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, it mentions the response includes autoConnectedRelationships. It doesn't specify if the element must exist, but that's implied by element_id. Overall sufficient for a straightforward add-to-view operation.

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%, but the description adds value by explaining auto_connect's purpose and stating that x/y default to auto, width=120, height=55, and that the response lists auto-drawn connections. This meaningfully extends the schema.

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 it adds an element to a diagram view and distinguishes itself from the sibling tool 'archimate_add_connection_to_view' by explaining auto-connection behavior.

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?

It explicitly says you do not need to call archimate_add_connection_to_view for relationships, and the auto_connect parameter provides guidance on when to set it to false. This gives clear when-to-use and when-not-to-use instructions.

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