base_flange

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent creation operation. The description adds useful context that it consumes an open or selected sketch and creates sheet metal geometry, but it does not disclose failure conditions, whether it creates a feature in the tree, or what happens when both an open and selected sketch exist.

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?

It is a single compact sentence with no wasted words, and the key action and source are front-loaded. Nothing is repeated from the schema or annotations.

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 creation tool that depends on an existing sketch and has sibling alternatives, the description is too sparse. An output schema means return values need not be explained, but prerequisites, interaction with edge_flange, and the meaning of undocumented parameters are missing.

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 schema describes three of four parameters well, but the description contributes no parameter semantics at all. The undocumented 'reverse_thickness' parameter is left without explanation in either the description or the schema, and the relationship between depth and open sketch profiles is not clarified further.

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 names a specific verb ('Creates') and resource ('sheet metal base flange / tab'), and it identifies the required source input ('open or selected sketch'). It is clear enough to distinguish from generic sketch or extrude tools, though it does not explicitly contrast with the nearby edge_flange sibling.

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 by the phrase 'from the open or selected sketch'; there is no explicit when-to-use guidance, no mention of prerequisites beyond the sketch source, and no routing to alternatives such as edge_flange or extrude.

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