Luaコンポーネント作成

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

The description discloses that code is syntax-validated before writing, and errors return an error. This goes beyond the minimal annotation (openWorldHint=false) by adding write behavior and validation.

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?

Two sentences: first states the action, second adds validation and return value usage. Front-loaded with key information, no superfluous text.

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 full schema coverage and an output schema, the description covers creation, validation, and integration with another tool. No gaps remain for an agent to invoke correctly.

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%, and the description adds extra context: name is without extension/path separator, code includes properties/OnStart/OnUpdate. This enriches the schema details.

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 explicitly states it creates a Lua component file in assets/components/. It also mentions the return value {path} for use in dx12_attach_lua_component, distinguishing it from sibling tools.

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 usage: when you need to create a Lua component. It mentions syntax validation and linking to dx12_attach_lua_component via the return value. However, it does not explicitly state when not to use it.

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