cad_extrude

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

No annotations are provided, so the description carries the full burden. It discloses the operation types (NEW/ADD/REMOVE/INTERSECT) and depth format, but fails to mention behavioral traits like modification of the document, required sketch state (closed), side effects, or error conditions. This is insufficient for a mutation tool.

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 minimal (two sentences) and front-loads the core purpose. It avoids redundancy but could be better structured by listing parameters. Overall, it is appropriately concise with no wasted words.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description lacks crucial context: return value, synchronous/asynchronous behavior, prerequisites (e.g., existing sketch), and failure modes. It is not complete enough for reliable agent usage.

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 0%, so the description must compensate. It explains 'operation' and 'depth' meanings but does not clarify the roles of documentId, workspaceId, elementId, sketchFeatureId, or name. Only 2 of 7 parameters gain context, leaving significant gaps.

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 states 'Extrude a sketch region' with a specific verb and resource. The operation enum and depth format add detail. However, it does not differentiate from sibling tools like cad_revolve, leaving some ambiguity about when to use this specific extrusion tool.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., cad_revolve for rotational extrusions). No conditions, prerequisites, or exclusions are mentioned, leaving the agent to infer usage from the bare purpose.

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