cityjson_remove_texturesRemoves all textures from a CityJSON dataset, returning a new dataset ID for further processing.
Remove all textures with cjio. Returns a new dataset_id.
| Name | Required | Description | Default |
|---|---|---|---|
| dataset_id | Yes | Dataset handle returned by cityjson_import, cityjson_open, cityjson_import_text, or another transformation tool. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the core effect and that a new dataset_id is returned, but does not disclose whether the original dataset is modified, whether removal is irreversible, or any side effects.
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 short and front-loaded with the key operation. The phrase 'with cjio' adds marginal value, but otherwise there is no wasted text.
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 simple one-parameter tool, the description covers the operation and the return value. However, with no annotations, no output schema, and no mention of side effects or alternatives, it remains minimally adequate rather than complete.
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 100% and the only parameter, dataset_id, is clearly documented in the schema. The description adds no parameter detail, but the baseline of 3 applies because the schema already handles the semantics.
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 verb and resource: 'Remove all textures'. This clearly identifies what the tool does and is enough to distinguish it from siblings like cityjson_remove_materials.
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 gives no guidance on when to use this tool versus alternatives. It does not mention cityjson_remove_materials, clean transformations, or any when-to-use/when-not-to-use context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.