debim_compile_ifc

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about whether the file at output_ifc_path is created, overwritten, or requires an existing directory, nor anything about error handling or permissions. It also gives no indication of how a malformed manifest is reported.

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 that states input and output crisply. It is efficient, though the terseness is part of why behavioral and parameter detail is missing.

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?

An output schema exists, so return values need not be explained, but for a tool that writes an artifact with zero annotation coverage and zero parameter documentation, the description leaves critical gaps: manifest format expectations, overwrite behavior, and where this fits relative to debim_validate.

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, but it only implies what the parameters are. It never explains the expected YAML manifest structure, required manifest keys, path format, or whether the output path must exist — the two most consequential inputs for getting a call right.

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 gives a specific verb ("Compile") and both the input resource ("declarative BIM YAML manifest") and the output artifact ("standard IFC4 building model"), so the transformation is unambiguous. It does not, however, differentiate itself from siblings like debim_validate or debim_generate_viewer, which also operate on the same BIM artifacts.

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 guidance on when to invoke this versus debim_validate (validate a manifest) or the cost/QTO tools, and no stated prerequisites such as validating the manifest first. The agent must infer the workflow ordering entirely from the tool names.

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