Create Instance

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

Annotations include openWorldHint: true, indicating potential side effects beyond the tool's immediate scope. The description does not add further behavioral details such as whether the original component is modified or what happens to overrides. It is adequate but does not exceed the information already provided by the annotation.

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 concise sentence that front-loads the essential action and key parameters. Every word is meaningful, with no redundancy or fluff.

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 the tool's complexity (6 parameters, 3 required, many siblings) and the existence of an output schema, the description is minimal. It does not explain what 'instantiate' entails (e.g., creating a new node instance), the role of parentId or parentNodeName, or any constraints. While not misleading, it leaves gaps that could be filled for full clarity.

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?

The input schema has 100% description coverage for parameters, so the baseline is 3. The description adds value by clarifying that componentKey and componentId are alternatives ('by ... or ...') and that x and y represent 'at a position'. This helps the agent understand the dual identification method beyond the schema's individual descriptions.

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 action (instantiate), the resource (component), and the identifying methods (by componentKey or componentId) and position. It effectively distinguishes from sibling tools like create_component which creates a new component rather than instantiating an existing one.

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 implies the tool is used when you want to place an existing component at a specific location, but it does not explicitly state when to use this over alternatives like create_component or instance_set_property. No usage exclusions or alternative tool names are provided.

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