sheet_metal_delete_flat_pattern

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

With no annotations, the description carries the full burden and does add real value: it discloses the failure mode (ENTITY_NOT_FOUND when no flat pattern exists) and the return shape. It does not say whether the deletion is undoable, what happens to the timeline feature, or whether dependent unfolds are affected — significant gaps for a destructive mutation.

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?

Front-loaded one-sentence purpose followed by compact error and return blocks; no filler. The fragment format ('Errors: ... Returns {...}') is terse but readable.

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?

Covers purpose, precondition failure, and return value, which is enough for a simple one-parameter tool. It remains thin for an unannotated destructive operation — reversibility, cascade effects, and permission requirements are all unaddressed.

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?

One optional parameter with 100% schema description coverage, so the schema already explains the component ref formats and the root-component default. The description adds nothing beyond 'a component's', which is the baseline for schema-covered parameters.

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 and resource: delete a component's flat pattern. An agent can distinguish it from sheet_metal_create_flat_pattern, sheet_metal_get_flat_pattern, and sheet_metal_unfold without opening the schema, though the description itself does not name those alternatives.

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?

Usage is only implied: the ENTITY_NOT_FOUND error note tells the agent the precondition is an existing flat pattern. There is no explicit when-to-use, when-not-to-use, or pointer to sheet_metal_unfold/refold as the non-destructive alternative.

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