cst_boolean_tool

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing. It does not say whether the input solids are consumed/merged, whether the operation is reversible, or what permissions are required. The only behavioral hint is the verb 'Combine', which implies mutation but leaves consequences unspecified.

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?

A single, front-loaded sentence with no filler; every word earns its place. It is efficient, though the terseness contributes to the gaps noted elsewhere.

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 4-parameter mutation tool with no annotations and 0% schema description coverage, the description is under-specified. It omits what target/tool refer to, what the operation values mean relative to those inputs, and the effect on the source solids; an output schema exists, so return values are the one area it need not cover.

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% and no parameter has an enum, yet the description only partially compensates by naming the operation values (add/subtract/intersect/insert). The required 'target' and 'tool' parameters are entirely unexplained, and even the operation values are given without mapping to the schema field.

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?

States a specific verb and resource ('Combine two solids') and enumerates the operation modes (add/unite, subtract, intersect, insert), which is clearly distinct from the many create_*/delete_solid siblings. It does not explicitly name a sibling it is not, but the boolean-operation framing is unambiguous.

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?

There is no when-to-use/when-not guidance, no mention of prerequisites (both solids must exist), and no routing to alternatives. The agent must infer usage entirely from the phrase 'Combine two solids'.

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