Save CityJSON

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'Copy' to a destination path and gives no information about overwrite behavior, side effects on the original dataset, error conditions, or what happens to associated resources like textures and materials.

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, front-loaded sentence with no filler or redundancy. It earns its place by giving the core operation and object, though it is concise at the expense of needed behavioral detail.

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 mutation-like save operation with no annotations, no output schema, and low parameter coverage, this description is too thin. It omits overwrite semantics, expected destination path format, and what the tool returns or confirms after saving, leaving an agent without enough context to invoke it confidently.

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 33%, and the description does not compensate. It hints at the destination parameter via 'destination path' and at the dataset_id via 'opened/derived dataset', but the overwrite parameter is completely unexplained, and destination lacks any semantic detail beyond its 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 clearly states the operation ('Copy') and target resource ('opened/derived CityJSON dataset') with an explicit outcome ('destination path'). It is specific enough to distinguish this from import/download/export siblings, though it does not explicitly name a differentiating alternative.

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 phrase 'opened/derived' implies the tool applies to datasets already loaded or produced by other tools, offering some usage context. However, there is no explicit guidance about when not to use it or how it compares to alternatives like cityjson_export or cityjson_download.

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