script_management

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

With only readOnlyHint=false in annotations, the description fails to disclose behavioral traits such as destructive side effects, permission requirements, or whether actions trigger recompilation, leaving significant gaps for safe agent decision-making.

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 well-structured with a clear verb phrase, bulleted categories, and action list, but it could be more concise by avoiding redundant listing of actions already in the schema.

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 complex tool with 8 parameters, no output schema, and diverse actions, the description lacks critical context such as return format for get actions, required parameter combinations per action, and behavioral nuances like platform defaults.

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 detailed parameter descriptions, so the description adds no additional meaning beyond the schema. Baseline of 3 is appropriate as it neither harms nor helps.

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 manages Unity scripting configuration and lists specific categories (define symbols, assembly definitions, execution order, compilation state) and actions, clearly distinguishing from sibling tools like execute_code and recompile_scripts.

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 through listing actions but does not provide explicit when-to-use or when-not-to-use guidance, nor does it differentiate from similar tools like recompile_scripts or scriptable_object.

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