material.create

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

Annotations already supply readOnlyHint=false, idempotentHint=true, and destructiveHint=true, so the safety profile is mostly structured. The description adds context about uniqueness and transaction-scoped creation, but it does not explain why destructiveHint=true applies or what effect creating inside a transaction has on existing scene state.

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 a single sentence with no filler or redundant restatement of the tool name. It front-loads the core action and scoping constraint. The main issue is not length but clarity of the specialized terminology.

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 four required parameters, no schema descriptions, and important sibling context around transactions and material workflows. The description does not connect create to transaction lifecycle concepts, idempotency, or scene generation expectations, so an agent lacks enough context to invoke it correctly in a real workflow.

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%, so the description carries the full burden of explaining parameters. It does not clarify transaction_id, expected_scene_generation, idempotency_key, or how the MaterialDefinition should be structured beyond the vague phrase 'bounded semantic surface values'. This is insufficient for an agent to confidently construct the required arguments.

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 a specific verb and resource: 'Create a uniquely named canonical Principled PBR material'. It also hints at a distinguishing constraint, uniqueness and being inside an 'active structural transaction', which helps separate it from material.set_input or material.assign. However, phrases like 'canonical' and 'bounded semantic surface values' are jargon-heavy and less operational than they could be.

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 implies a prerequisite: the creation must happen 'inside the active structural transaction'. This gives some context about when the tool is appropriate, but it does not explicitly say when to prefer this over siblings such as material.set_input, material.assign, or transaction.begin, nor does it state any exclusions.

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