geometry_build

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

No annotations provided; description mentions it is a build operation (likely mutable) and requires prior modifications. However, it does not detail destructiveness, permission needs, or reversible nature.

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?

Two short, efficient sentences. The first clearly states purpose and prerequisite, the second lists parameters. No wasted text.

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?

No output schema; returns are only 'Build status' without detail. No mention of possible failures or side effects. Adequate for a simple tool but lacks completeness for a production setting.

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 has 0% coverage (no descriptions), but the description adds meaning for each parameter: defaults for geometry_name (build all), component_name ('comp1'), model_name (current model).

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?

Clearly states the tool builds the geometry sequence to generate the actual geometry, and distinguishes from sibling tools that add/modify features (e.g., geometry_add_block).

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?

Explicitly states 'must be called after adding/modifying geometry features', providing clear context. Does not mention alternatives, but the sister list of geometry modification tools implies when to use others.

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