cst_array_linear

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

The description discloses the method (Transform.Translate) and naming convention, but does not reveal important behaviors: whether it modifies the original element, creates a new assembly, or requires pre-existing elements. Without annotations, more detail is needed for full transparency.

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, front-loaded with purpose. No wasted words. Efficiently conveys the core action and a key implementation detail.

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?

Covers the creation action but lacks context about prerequisites (e.g., element component must exist), output, and side effects. No output schema, but given complexity, more behavioral context is expected for completeness.

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 the baseline is 3. The description adds minimal extra meaning beyond the schema; it mentions 'along a chosen axis' and naming convention, but does not elaborate on parameter formats or dependencies.

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 tool creates a linear antenna array by replicating an element along an axis, which distinguishes it from circular or planar array tools. However, it does not explicitly contrast with sibling tools like cst_array_circular or cst_array_planar.

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?

No guidance on when to use this tool vs alternatives like cst_array_circular or cst_array_planar. No prerequisites are mentioned (e.g., existence of an element component). The description only states what it does, not when to use it.

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