model_create_component

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

With no annotations, the description carries the full behavioral burden; it discloses that components are containers for geometry/physics/materials/mesh and that creation is a prerequisite, which is useful semantic context. It is silent on failure modes (duplicate component name), whether the new component becomes current/active, and persistence, leaving meaningful gaps for a mutation tool.

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 Args/Returns layout is easy to scan and front-loaded, but the ordering constraint is stated twice — '(required before adding geometry/physics)' and then 'Must be created before adding geometry or physics' — so one sentence does not earn 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 simple three-parameter creation tool with no output schema, the description covers purpose, precondition, and every parameter, and summarizes the return ('Created component info'). It is only mildly short of complete given the absence of any statement about duplicate-name behavior or error responses.

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, and it does: it documents all three parameters with defaults and, critically, decodes the non-obvious space_dimension integer codes (0/1/2/3/20/30 = 0D..3D axisymmetric) that the bare integer schema cannot convey.

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?

States a specific verb+resource ('Create a component in the model') and immediately scopes it with the precondition that it must precede geometry/physics. This distinguishes it from siblings like model_create, geometry_create, and model_list_components without opening any schema.

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?

Gives an explicit ordering rule ('Must be created before adding geometry or physics'), which is genuine when-to-use guidance for an agent sequencing a modeling workflow. It does not name an alternative tool or state when-not to use it, but the precondition covers the primary decision point.

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