unity_script_create

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

The description does not mention behavioral traits beyond creation, such as whether it overwrites existing files, requires permissions, or triggers compilation. Without annotations, the agent has minimal insight into side effects.

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 efficient sentence that conveys the core purpose without redundancy. It is front-loaded and earns its place, though slightly more structure could help.

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 file-creation tool with four parameters and no output schema, the description covers the basics but omits critical context like overwrite behavior or post-creation implications, leaving gaps for the agent.

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 coverage is 100% with all four parameters described. The description adds no additional meaning beyond the schema, meeting the baseline for parameter semantics.

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 verb 'Create', the resource 'new C# script file', and the context 'in the project with the given content'. It distinguishes the tool from siblings like unity_script_read and unity_script_update.

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 provides no guidance on when to use this tool versus alternatives, such as using unity_script_update for modifying existing scripts. It lacks explicit context for when-not-to-use or exclusions.

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