shaderfx.list

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

With no annotations, description implies a read-only listing operation. It does not disclose failure behavior (e.g., non-Grease Pencil object) or return format, but for a simple list tool this is minimally adequate.

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?

Single sentence with no fluff, front-loaded with action and target. Every word is necessary.

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 simple list tool with one parameter and no output schema, the description covers the basics. Could be more complete by stating return format or error cases, but adequate.

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 description coverage is 0%, but the description adds context that the object is a Grease Pencil object. The title 'Object to inspect' in the schema is also helpful. Since there is only one parameter, the description compensates moderately.

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?

Description clearly states it lists shader effects on a Grease Pencil object, using a specific verb and resource. However, it does not distinguish from sibling tool shaderfx.report, which likely also displays shader effects.

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 on when to use this tool versus alternatives like shaderfx.report. No prerequisites or conditions mentioned (e.g., object must be Grease Pencil).

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