mod_extrude

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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds that this is a modifier-based operation on a profile/face, but does not disclose side effects such as modifying the modifier stack or how existing geometry is affected.

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 with the core purpose, and contains no filler. The bilingual structure is somewhat redundant but still compact and appropriate for the tool's audience.

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 schema fully documents parameters and annotations cover the destructive nature, so the main gaps are usage guidance and behavioral side effects. The description is adequate for a basic call, but it does not explain the difference from similar extrude tools or the full modifier-stack impact.

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 100%, so parameters are well documented there. The description repeats amount, segments, capStart, and capEnd but adds no new semantic meaning beyond what the schema already 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 a specific operation: 'Extrude modifier: push a profile/face into a solid along an axis'. The word 'modifier' distinguishes it from sibling tools like poly_extrude_faces and model_extrude_spline, though it does not explicitly 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?

No guidance is given on when to use this tool versus similar siblings such as poly_extrude_faces or model_extrude_spline. There is no mention of prerequisites, selection behavior, or when not to use the modifier.

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