model_create_component

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

With no annotations, the description carries full burden. It states creation and containers role but omits side effects (e.g., duplicate component behavior), permissions, or return value details.

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 with a clear opening sentence. The Args section is somewhat redundant but not overly long. Could integrate parameter info more efficiently.

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 2 params and no output schema, the description covers the core purpose and preconditions. However, it lacks error handling, explanation of 'current model', or what happens on re-creation.

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 description must compensate. It redundantly repeats the default values already in schema and adds only minimal context ('default: current model'). Does not explain 'model_name' null behavior or validation.

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 the tool creates a component and establishes it as a prerequisite for geometry/physics, distinguishing it from sibling tools like geometry_create or mesh_create.

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 explicitly says 'required before adding geometry/physics' and 'Must be created before adding geometry or physics', providing clear usage context. It does not discuss when not to use it, but the priority is evident.

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