Create RayTK SDF graph

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

Annotations already indicate non-read-only (readOnlyHint=false), open-world (openWorldHint=true), and non-destructive (destructiveHint=false) behavior, so the description does not need to repeat those. It adds meaningful context by specifying the prerequisite staging and the exact graph structure. Yet it does not disclose potential failure modes (e.g., behavior if RayTK is not staged) or side effects beyond building the graph, so a middle score is appropriate.

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 two sentences long, with the first sentence delivering the complete action and component list, and the second giving the essential prerequisite. Every clause carries necessary information; there is no fluff or repetition. It is well-organized and front-loaded with the core purpose.

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?

With 10 parameters and no output schema, the description does a good job of providing a clear mental model of the resulting graph and the one critical prerequisite. It could optionally mention what a successful return looks like or clarify 'copied masters' operationally, but given the rich schema and the non-destructive annotation, the description is sufficiently complete for an agent to invoke it correctly.

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 schema has 100% description coverage for all 10 parameters, so the baseline is 3. The description adds a high-level grouping of parameters (primary, secondary, material, lights, etc.) but does not provide per-parameter details beyond what the schema already offers. It satisfies the baseline without surpassing it.

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 explicitly states 'Build a RayTK SDF graph' and enumerates the exact constituent nodes (primary SDF, optional secondary, material, camera, light, renderer, Null TOP), making the tool's purpose and scope unambiguous. This clearly differentiates it from sibling tools like create_raytk_op, which likely creates a single RayTK operator, by specifying a multi-node graph assembly.

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 provides clear usage context by stating the prerequisite: RayTK must be staged via 'manage_packages install raytk' and loaded from the staged .tox. It also implies the source materials are 'copied RayTK ROP masters.' However, it does not explicitly mention when to choose this tool over alternatives (e.g., create_raytk_scene), so it stops short of a full 5.

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