create_symmetry_bc

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says the tool creates a symmetry BC and lists symmetry_type values; it does not describe what applying the BC does, which regions/faces it applies to, side effects, validation behavior, or whether it mutates existing model state. For a mutation tool, this is a significant transparency gap.

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 text is short and front-loaded with the core purpose, which is good. However, the 'Args' block lists only one of six parameters and is presented as a complete argument doc, which is structurally misleading. The conciseness is achieved at the expense of necessary parameter information.

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?

For a tool with six parameters, no annotations, and no schema-level parameter descriptions, the description is far too thin. It lacks any explanation of required inputs, defaults, or how the symmetry_type choices affect the created BC. The list of symmetry_type constants provides some domain context, but an agent cannot reliably invoke this tool correctly from this description alone.

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 0%, so the description must compensate. It adds useful allowed values for symmetry_type, but this is the only parameter documented despite there being six parameters. Crucially, the required parameters name and region_name are never mentioned, which could lead an agent to omit them. The partial 'Args' section overstates its completeness.

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 a specific action ('Create') and a specific resource ('a symmetry boundary condition'), which distinguishes it from sibling BC tools like create_encastre_bc or create_displacement_bc. It also lists the meaningful symmetry type variants, giving the agent a clear sense of the tool's domain. However, it does not explain what each symmetry type means or how this BC behaves physically.

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 provides no guidance on when to choose this tool over the many sibling boundary condition tools. It does not mention applicability, prerequisites, or scenarios where a symmetry BC is appropriate versus an encastre, displacement, or pinned BC. The agent must infer usage solely from the tool name and the symmetry_type values.

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