Import CityJSON into cjdb

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the tool converts to CityJSONSeq with cjio, imports via cjdb, and requires PGPASSWORD rather than a password argument. However, it does not disclose side effects on the database, such as whether existing tables are overwritten, whether the schema is created, 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?

Two sentences, front-loaded with the main action and the operational security requirement. There is no fluff or redundant restatement. Every sentence contributes necessary information.

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?

This is a database import operation with no annotations, no output schema, and incomplete parameter documentation. The description omits important context such as the meaning of attribute indexes, what happens on conflicts, whether the operation is idempotent, and what the success or failure response looks like. It is not complete enough for an agent to invoke the tool confidently in all realistic cases.

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 only 25%, with only dataset_id documented. The description does not explain the connection object fields, attribute_indexes, or partial_attribute_indexes beyond the schema's minimal structure. It adds the PGPASSWORD context, but that does not compensate for the lack of meaning for most parameters.

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 clearly states the action: convert the dataset to CityJSONSeq with cjio and import it into PostgreSQL/PostGIS using cjdb. This gives a specific verb, resource, and target database. It does not explicitly name sibling alternatives like cityjson_db_export, but the import direction is clear enough to distinguish it from export-related tools.

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 implies the tool is used when a dataset should be loaded into a PostgreSQL/PostGIS database. It also gives a prerequisite: the PostgreSQL password is supplied via PGPASSWORD. However, it does not explicitly state when to use this tool over alternatives, such as cityjson_db_export or other transformation tools.

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