shader_list

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

The annotations already declare readOnly, idempotent and non-destructive, so '[INSPECT] Read-only.' is largely redundant. The one piece of added value is stating what is returned ('compiled shader programs with their materials'), which matters because no output schema exists; beyond that there is no pagination, size, or auth context.

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 short fragments with the category tag front-loaded and no filler prose. The '[INSPECT] Read-only.' line duplicates annotation data rather than adding information, a minor waste, but the overall size is appropriate.

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 parameterless read-only list tool with annotations covering the safety profile, the description is mostly sufficient. It is thin on routing (why this vs shader_source or material_list) and gives no sense of the returned list's shape, though no output schema is provided to carry that burden.

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 tool takes zero parameters, which per the rubric sets the baseline at 4. There is nothing for the description to document beyond this.

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 phrase 'Compiled shader programs with their materials (WebGL)' states the resource and scope clearly, and the name/verb 'list' is implied. It does not explicitly distinguish itself from the close sibling shader_source, which presumably returns source code rather than the compiled program list.

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 or when-not guidance and no mention of the adjacent siblings (shader_source, material_list, material_details). The agent is left to infer selection criteria from the name alone.

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