Create Instance

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

The annotation openWorldHint suggests side effects, but the description does not disclose any behavioral traits beyond 'instantiate'. No mention of destructive potential, permissions, or effects on existing instances. Annotations provide minimal context, and the description adds little.

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 sentence that front-loads the main action. Every part is purposeful with no wasted words.

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, output schema, many siblings), the description is brief. It does not explain the return value (though output schema exists) or error scenarios. More guidance on when to use this vs siblings would improve completeness.

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 100%, so the schema already documents all parameters. The description adds 'preferred for local components' for componentId, which adds some nuance, but overall does not significantly add meaning beyond the schema.

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 it instantiates a component by componentKey or componentId at a position. It uses a specific verb and resource, and distinguishes from sibling tools like create_component.

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 does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. It implies usage for creating an instance, but lacks guidance on choosing between componentKey and componentId or when to set parentId.

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