Generate a structure from a preset

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

With no annotations, the description carries full burden. It discloses that the tool creates geometry, sections, supports, and loads, which is a clear behavioral summary. It could mention side effects like overwriting existing models, but the 'Create' verb implies no destruction.

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 first sentence packs the core action and options; the second adds a crucial reference. Every word earns its place.

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 complex parametric generation tool with no output schema, the description covers preset list, param override behavior, and the creation scope. It could mention that the output is a model object, but the completeness is high.

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 baseline is 3. The description adds value by listing available presets and explaining that params override defaults with an example, going beyond bare schema definitions.

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 uses a specific verb ('Create') and resource ('complete model... from a parametric typology preset'), listing exact presets like truss_bridge and noting parameter overrides. It clearly distinguishes from siblings like create_model and list_structure_presets.

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 states that params override preset defaults and directs to list_structure_presets for details, providing clear context for use. However, it does not explicitly exclude cases or mention alternatives beyond the preset listing.

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