recipe.update_procedural_courtyard

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

Annotations provide little information (all false), so the description carries the burden of behavioral disclosure. The description adds only generic operational context ('Risk: standard; maturity: L3; Requirements') but never states what the tool does, what side effects it has, or what gets modified. This is a marginal improvement over nothing.

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, but it is under-specified rather than concise. It only restates the name and adds boilerplate risk/maturity info, so the sentence does not earn its place by conveying useful information.

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?

For a complex tool with 8 parameters and an output schema, this description is severely incomplete. It omits any statement of the operation's purpose, prerequisites, or effects, leaving the agent without enough context to decide whether this tool applies.

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 description mentions zero parameters. With schema description coverage at 50%, several parameters (like dims, rubbleDensity) lack documentation, and the description does not compensate for this gap. It adds no meaning to the input schema.

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 essentially restates the tool's title ('PartMe Blender Harness command `recipe.update_procedural_courtyard`') without explaining what the command actually does. It lacks any verb+resource description beyond the name itself, so an agent cannot infer its function.

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?

There is no guidance on when to use this tool versus alternatives like blender_recipe_procedural_courtyard or other recipe tools. No conditions, prerequisites, or exclusions are mentioned.

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