check_collision

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool reports intersection volume, which is a useful behavioral detail, but it does not explicitly confirm the operation is read-only, describe units, or mention failure behavior. This is adequate but not rich.

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 a single efficient sentence with no filler. It front-loads the core action and immediately states the reported result.

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 is clear at a high level and the presence of an output schema reduces the need to describe return values. However, because there are no annotations and no parameter descriptions, important operational context is missing: whether object_a/object_b are names or geometry, whether a document must be specified, and what tolerance means.

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 for missing parameter documentation. It maps 'two shapes' to object_a and object_b, and 'intersection volume' to the result, but it does not explain what the strings represent, how tolerance is used, or the role of doc_name.

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 uses a specific verb ('Check') and resource ('two shapes'), and adds a concrete output ('intersection volume'). It is clear what the tool does, though it does not explicitly distinguish it from siblings like check_geometry or boolean_common.

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?

No guidance is provided about when to use this tool versus siblings such as check_geometry, get_bounding_box, or boolean_common. The intended use is implied by the wording, but alternatives and conditions are never discussed.

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