mod_smooth

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

The annotations already communicate readOnlyHint=false and destructiveHint=true, so the agent knows the operation mutates. The description adds some behavioral context by tying autoSmooth to threshold-based smoothing and the other mode to angle-based smoothing groups, but it does not disclose consequences such as stack changes, reversibility, or what happens to existing smoothing groups.

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 short, front-loaded, and contains no filler. The bilingual repetition is slightly redundant but still compact and appropriate for a multilingual tool surface.

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 description, schema, and annotations together provide a basic understanding of the tool's purpose and mutating nature. However, with no output schema, the description does not mention return behavior, and it also omits how the modifier is applied to the named/selected objects or what exactly becomes destructive. It is adequate but not fully complete for a 5-parameter mutation tool.

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 the schema already documents all parameters well. The description adds only modest semantic value by connecting autoSmooth to threshold-based behavior versus angular smoothing groups, but it does not elaborate on smoothness, defaults, or object selection behavior beyond what the schema provides.

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 identifies this as a Smooth modifier and describes its two operating modes: auto-smooth by threshold and smooth by angle/smoothing groups. It is not a pure tautology because it explains the behavior, but it lacks an explicit operation verb such as 'adds' or 'applies', and it does not differentiate itself from sibling tools like mod_turbosmooth or poly_auto_smooth.

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?

No guidance is given about when to use this tool versus alternatives. The description explains what smoothing does but provides no exclusions, prerequisites, or pointers to related tools such as mod_turbosmooth, poly_auto_smooth, or poly_set_smoothing.

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