shader

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

Annotations are minimal and description adds little beyond listing actions. No disclosure of side effects, permissions, or behavioral traits for operations like 'write' or 'create'.

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?

Description is very short and to the point, but the reference to help tool reduces its self-contained value. It's not verbose, but omits critical details.

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 no output schema and multiple actions, the description is grossly incomplete. It fails to explain what each action does, what the return values are, or any prerequisites, leaving the agent to rely on an external help tool.

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?

Input schema has 100% coverage with descriptions for all parameters, so baseline is 3. The description repeats the action enum list but adds no additional meaning beyond what schema already provides.

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 clearly states it's for 'Godot shader management' and lists available actions, distinguishing it from sibling tools focused on other areas like animation or audio.

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?

Provides no guidance on when to use this tool versus alternatives, nor when not to use it. Only directs to 'use help tool for full docs', which does not constitute usage guidelines.

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