script-update-or-create

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

Discloses key behaviors: AssetDatabase.Refresh() and compilation error details. However, no annotations exist, and it omits potential side effects like overwriting files or permission requirements.

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?

Three sentences, each adding value: purpose, side effects, and usage advice. No extraneous words, front-loaded with primary action.

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?

Covers main behaviors and provides a usage hint. Lacks return value specification (e.g., whether errors are returned). Acceptable given complexity and no output schema.

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 provides descriptions for 2 of 3 parameters (67% coverage). Description adds no new semantic information beyond repeating schema content. Baseline score is appropriate.

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?

Description clearly states the tool updates or creates script files with C# code, and distinguishes itself from sibling 'script-read' by advising to read first. Verb+resource is specific and actionable.

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?

Explicitly recommends using 'script-read' before this tool, providing clear context. Does not specify when to choose update vs create, but the recommendation is helpful for workflow.

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