基本色設定

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

Beyond the idempotent annotation, the description discloses the multiplicative behavior with vertex color and combination with PBR, adding valuable context. No contradictions with annotations.

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 (3 sentences) and front-loaded: first sentence states purpose, second gives use cases, third provides color format and combination hint. No unnecessary words.

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 tool has an output schema (not shown), so return values are covered. The description covers purpose, parameters, usage context, and relationship to siblings. Missing edge cases (e.g., behavior if entity not found) but schema constraints and simplicity mitigate this.

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?

With 100% schema coverage, the description still adds extra meaning: color bounds [0..1], an example value for gold, exclusive nature of entity and name, and stability of name after Stop. This exceeds the baseline 3.

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 sets the base color (multiplied with vertex color) of meshes, with specific use cases (scaffolds, coins) and a concrete color format [r,g,b](0..1). It distinguishes itself from sibling tools like dx12_set_pbr by mentioning combined usage, making it unique.

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?

The description gives explicit context for when to use this tool (coloring scaffolds/coins) and directs users to dx12_set_pbr for metalness (metallic/roughness). However, it lacks explicit 'when not to use' statements, though the mention of alternatives implies exclusions.

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