geometry_boolean_difference

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

With no annotations, the description bears full burden. It states the operation creates a difference and mentions default behaviors (e.g., feature_name auto-generated). However, it does not disclose whether the operation is destructive, reversible, or requires specific model states.

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 uses a clear docstring format with Args and Returns. It is moderately concise but could be slightly shorter for an AI agent (e.g., simplified examples). No wasted sentences.

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 covers the main functionality and parameter explanations. However, it lacks details on edge cases (e.g., non-intersecting objects), error handling, or the return value structure beyond 'difference operation info'. Given no output schema, more context would help.

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 0%, so the description must compensate. It provides meaningful examples (e.g., 'blk1', ['cyl1']) and explains default values for optional parameters. This adds significant value beyond the schema, though some parameters (e.g., geometry_name) could be further clarified.

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 name and description clearly indicate the tool performs boolean difference (subtract objects). The description explicitly states 'Create a boolean difference (subtract objects from another)', and it distinguishes from sibling 'geometry_boolean_union' by specifying subtraction rather than union.

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 basic usage (e.g., what each parameter represents) but does not specify when to use this tool over alternatives like boolean union or other geometry operations. There is no guidance on prerequisites or conditions for use.

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