apply_material_recipe

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

Annotations already disclose readOnly=false and destructive=false, so the safety bar is lowered. The description adds incremental context: it says overrides are constrained, and it explains the default fresh-tab behavior. But it does not explain whether applying is reversible, what validation failures look like, or the effect on overrides against non-declared parameters beyond 'may only target'.

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, front-loaded with the core action ('Validate and apply...'), then scoped constraints. No filler. It is efficient, though it could be slightly terser and better organized for scanning.

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?

An output schema exists, so return values need not be explained. But five parameters with zero schema descriptions mean the description leaves gaps around position, material_id, and recipe_id, and it does not state whether validation is automatic or what happens on invalid recipes. Complete enough for a simple apply tool, but not fully self-sufficient.

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 coverage is 0%, so the description must carry semantics. It correctly documents override keys as Node.parameter and constrains overrides to parameters already declared by the recipe, which is meaningful. It also implies default create_new=true behavior and why it exists. However, position and material_id semantics are absent, and the description does not explain what recipe_id must reference.

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 compound action: validate AND apply a 'curated recipe', and scopes it further with 'optionally with constrained parameter overrides'. It distinguishes itself from siblings like list_material_recipes/describe_material_recipe by being the writer/application step. It doesn't explicitly name those siblings, so this is not a 5.

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?

Important usage is implied via 'By default a fresh material tab is created to avoid replacing existing inputs', which hints at a mutation workflow and a safe default. But there is no explicit when-to-use vs. alternatives, no mention of list/describe recipes as a prerequisite, and no exclusion guidance. Adequate but with clear gaps.

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