create_post_process_material

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered. The description goes beyond them by enumerating the outcome state flags (created, already_exists, saved), which tells the agent the call may be a no-op returning an existing asset and may or may not persist to disk — genuinely useful behavioral context. It stops short of stating permission requirements or whether the in-memory asset needs a separate save.

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 sentences, purpose first, with zero preamble. The inline return signature is dense but earns its place because no output schema exists. Slightly compressed formatting, but nothing is wasted.

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?

Since there is no output schema, inlining the return fields (material_path, is_post_process, created, already_exists, saved) is exactly what the agent needs to interpret results. What is missing is whether the target package directory must pre-exist and whether the new asset is persisted to disk or only created in memory — the 'saved' flag hints at the latter but does not explain it.

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 100%, so both parameters (name, package_path) are already documented with meaning and example format in the schema. The description adds no parameter syntax or constraints beyond restating package_path in the return payload, so baseline 3 is appropriate.

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?

States a specific verb (Create), a specific resource (UMaterial) and the distinguishing configuration ('post-process material (MD_PostProcess)'), which separates it from the many other material-creation siblings such as create_material or create_material_instance. An agent can tell what asset type this produces without opening the schema.

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 never says when to choose this tool over create_material / create_material_instance, nor what prerequisites (existing package directory, project settings) are required. The domain qualifier implies the use case but no explicit when/when-not guidance or alternative routing is provided.

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