manage_shader

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

The description discloses that the tool can create or read files, but with no annotations provided, it fails to explain behavioral details like whether 'create' overwrites existing files, error handling, or return behavior. Important context is missing.

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 one concise sentence that immediately states the tool's purpose. It is front-loaded and free of unnecessary words, though it could benefit from slightly more structure.

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?

With five parameters and no output schema or annotations, the description is too brief. It omits return values, error conditions, and nuances between create and read actions, making it insufficient for confident tool invocation.

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?

All five parameters are described in the input schema with 100% coverage. The description does not add clarity beyond the schema descriptions, so it meets the baseline for adequate parameter understanding.

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 'Create or read .gdshader files' with a specific verb and resource, clearly indicating two main actions. It distinguishes the tool from siblings like 'game_visual_shader' or 'create_resource' by focusing on .gdshader files, though it doesn't explicitly differentiate from other file management tools.

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?

No guidance is provided on when to use this tool versus alternatives such as 'write_file', 'read_file', or 'create_resource'. There is no indication of prerequisites, constraints, or scenarios where this tool is preferred.

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