Convert CityJSON to CityGML

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

With no annotations provided, the description carries the full burden. It does add useful behavioral context: the conversion is delegated to 'citygml-tools' and the installed version influences the target encoding. However, it does not disclose whether the source dataset is modified, whether an output file is created, what happens in the output_directory, or what the tool returns.

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 two sentences long, front-loaded with the core conversion intent, and every sentence adds useful information. The second sentence about citygml-tools version and target encoding is relevant and non-redundant.

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 not fully complete for an agent: there is no output schema, no annotations, and the description omits how optional parameters affect behavior, what the result of the conversion is, and how output is stored or returned. For a conversion tool with three parameters and no structured output metadata, this leaves significant gaps.

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 low: only dataset_id is described, while crs_name and output_directory have no schema descriptions. The tool description does not compensate by explaining these parameters, leaving their exact semantics ambiguous, especially crs_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 states a specific action ('Convert'), the input ('an opened CityJSON dataset'), the output format ('CityGML'), and the implementation tool ('citygml-tools'). This clearly distinguishes it from the reverse sibling tool 'citygml_to_cityjson' and from import/export variants that do not perform this exact conversion.

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 clearly establishes the prerequisite that the dataset must already be opened/imported, which tells the agent when the tool is applicable. It does not explicitly mention alternative tools such as 'cityjson_export' or when not to use this tool, so it stops short of full routing guidance.

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