Tuanjie Script Manager

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description honestly lists non-destructive actions (read, validate) alongside destructive ones (update, delete), so there is no contradiction. It adds the 'under Assets' scope but does not explain side effects, file rewrite behavior, or Unity refresh implications.

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 concise and front-loaded with the resource and operations. The action list is slightly redundant ('update', 'edit', 'apply_text_edits' overlap), but there is no filler or unnecessary length.

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 multi-action destructive file-management tool with an open additionalProperties schema and no output schema, this is incomplete. It omits per-action parameter expectations, return values, and behavioral outcomes, so an agent cannot reliably invoke it without guessing.

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?

The schema has zero description coverage and only defines the action enum. The description says additional action-specific parameters are passed through unchanged, which is useful but vague; it does not name or document the parameters required for each of the eight actions, leaving a significant gap.

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 states a specific resource ('C# scripts under Assets') and a clear set of operations (create, read, edit, validate, delete), so an agent knows what the tool manages. It doesn't explicitly contrast with sibling tools like execute_csharp_script or unity_shader, but 'C# scripts under Assets' scopes it well enough.

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?

There is no guidance on when to use this tool versus alternatives such as execute_csharp_script or unity_custom_tools. The description does not mention prerequisites, exclusions, or when each action should be preferred.

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