Tuanjie Shader Manager

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

The description adds the useful behavioral note that action-specific parameters are passed through unchanged, and it lists the action categories, which goes beyond the annotations. However, it stays silent on the concrete effects of compile or preview despite destructiveHint=true, so agents get no context about what may be modified.

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 concise sentences with no filler; the supported actions and pass-through behavior are front-loaded. It is compact, though it could use a bit more per-action detail without becoming bloated.

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 dispatcher with no output schema and no parameter documentation, this is under-specified: per-action inputs, outputs, side effects, and failure modes are absent. The enum names convey intent but not enough to invoke compile or ensure_material_shader_for_srp 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 parameter coverage is 0% and the description mostly restates the action enum already present in the schema. The note that extra parameters are passed through is informative but does not tell the agent what parameters each action expects, leaving the additionalProperties space completely undocumented.

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 opens with a clear verb-and-resource statement, 'Inspects render pipelines and manages shader compilation or previews', and enumerates all four supported actions, distinguishing it from the sibling asset/package/scene tools. It is not a 5 because the individual actions are only named, not explained, so an agent still has to infer what each one does.

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 when-to-use guidance or comparison with alternatives such as execute_csharp_script or unity_menu. The phrase 'Inspects render pipelines' gives a rough context, but nothing tells the agent when to prefer this tool over a sibling or 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.