Convert CityGML to CityJSON

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

With no annotations, the description carries the full burden, and it does disclose a meaningful side effect: the output is 'automatically registered and returned by filename,' which tells the agent a backend record is created and what the return value is. It says nothing about write locations, overwrite behavior, or failure modes for unsupported/invalid GML.

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 tight sentences with the conversion scope front-loaded; 'using citygml-tools' is a minor implementation detail but justifies the version list. No filler or repetition.

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 tool with zero schema coverage, no output schema, and a second boolean parameter, the description leaves too much unspecified — notably the meaning of 'source' and the effect of 'json_lines.' It covers the happy path and the registration side effect but not enough for confident invocation.

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, and it largely does not. It never explains whether 'source' is a filesystem path, an uploaded file id, or a registered name, and it omits the 'json_lines' flag entirely, leaving the agent to guess that it produces CityJSONSeq-style output.

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 ('Convert a CityGML 1.0/2.0/3.0 GML/XML file to CityJSON'), including the supported input versions, so the direction of conversion is unambiguous and clearly the mirror of cityjson_to_citygml. It does not explicitly name the reverse sibling, but the conversion direction alone is enough to distinguish it.

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?

Usage is only implied: an agent infers it should call this when it holds a CityGML file. There is no explicit when-to-use, no statement of when NOT to use it, and no differentiation from nearby tools such as cityjson_import or cityjson_import_text that could plausibly also take external data.

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