etabs_new_model

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

Annotations already declare destructiveHint=true, indicating potential to overwrite. The description adds the template option but does not disclose that creating a new model may close an existing unsaved model, nor does it mention required permissions. Additional context would improve 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 concise, front-loaded with the core purpose, and presents parameters in a clear, structured list. Every sentence is necessary and efficiently conveys 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?

Given 9 parameters and zero schema descriptions, the description covers all parameter semantics. It mentions return value. However, it could mention that creating a new model closes the current one, which is implied by destructiveHint. Overall, it is sufficiently complete for a creation tool.

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 fully explains all 9 parameters, including units with enumerated values, template types, story heights, and bay dimensions. This adds significant meaning beyond the schema's property names and 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 clearly states 'Create a new ETABS model, optionally from a template.' The verb 'Create' and resource 'new ETABS model' are specific and distinct from sibling tools like etabs_open_model and etabs_save_model.

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 implicitly indicates creation of new models, but does not explicitly exclude alternatives or state when to use versus etabs_open_model. The mention of 'optionally from a template' provides some context, but lacks direct guidance.

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