create_pinned_bc

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

With no annotations, the description carries the behavioral burden. It discloses the core semantic (translations fixed, rotations free), but omits side effects such as whether the BC replaces existing constraints, whether the target region must already exist, or what the tool returns. For a mutating create operation, this is only partial 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?

The description is a single, tightly packed sentence with no filler. It front-loads the action and the key constraint detail, making it easy to parse quickly.

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?

Although an output schema exists, the description is too thin for a 5-parameter creation tool: it neither explains the required parameters nor the prerequisites or application context (e.g., region must exist). An agent would likely need to inspect sibling tools or experiment to call it correctly.

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%, and the description does not mention any of the five parameters. An agent gets no help understanding what 'name' refers to, how 'region_name' selects the region, or what 'timeout', 'step_name', and 'model_name' contribute beyond their schema titles/defaults.

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 verb ('Create'), the resource ('a pinned BC'), and the exact constraint behavior ('U1=U2=U3=0, rotations free'). This clearly distinguishes it from sibling boundary-condition tools like create_encastre_bc, which would fix rotations as well.

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 usage context is implied by the DOF definition—use this when you need a pinned support with free rotations—but no explicit when-to-use or when-not-to-use guidance is given. It does not name alternatives like create_displacement_bc or create_encastre_bc as options to compare against.

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