shaderfx-list

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

No behavioral annotations are provided. The description implies a read-only operation, but it does not explicitly state that it has no side effects or require specific permissions, which would be helpful.

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 to the point, with no unnecessary words. It effectively communicates the tool's purpose in a single sentence.

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?

The description is adequate for a straightforward listing operation, but it does not mention what the output will contain (e.g., list of shader effect names, properties). This could be clarified, though it is not critical for basic usage.

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 parameter 'object' is described as 'Object to inspect', which is minimal but sufficient for a simple list operation. It does not elaborate on acceptable formats or potential defaults.

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 specifies the action (list) and the resource (shader effects on a Grease Pencil object), distinguishing it from sibling tools like shaderfx-add and shaderfx-remove.

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 given on when to use this tool versus alternatives such as shaderfx-report, which might also provide similar information. The description lacks context for selection.

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