カスタムシェーダー読み取り

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

The description reveals the output includes path, code, and compiled status, which goes beyond the readOnlyHint annotation. It explains the behavioral trait that the output shows last known compile success, adding valuable 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 concise sentences: first states the core functionality, second provides usage context and output format. No unnecessary words; every sentence is informative.

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 read tool with one parameter and an output schema, the description covers purpose, usage differentiation, and output fields. It is complete without needing additional details.

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?

While the input schema fully describes the path parameter (100% coverage), the description adds value by detailing the output structure, indirectly clarifying the parameter's role. The baseline is 3, and the extra context justifies a 4.

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 the tool reads existing custom shaders (.hlsl) as-is, distinguishing it from the sibling dx12_create_shader which is write-only. The verb 'read' and resource 'custom shader' are specific and unambiguous.

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?

Explicitly notes that dx12_create_shader is for writing and this tool is for reading, making the edit loop clear. It provides a direct when-to-use and when-not-to-use scenario.

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