cityjson_attribute_removeRemove a named attribute from all CityObjects in a CityJSON dataset to clean unwanted properties while preserving geometry.
Remove an attribute across CityObjects with cjio.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| 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?
With no annotations, the description carries the full burden of behavioral disclosure. It communicates that this is a removal/mutation operation but does not say whether it is irreversible, whether it operates in memory, what happens if the attribute does not exist, or what the return value is.
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 focused sentence with no filler. It front-loads the core action and resource, making it easy to scan.
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 tool with no annotations and no output schema, the description is too thin. It omits important operational context such as the effect on the dataset, whether the operation is reversible, and what the tool returns, leaving an agent to infer key behavior from the sibling tool family.
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 coverage is 50%, with dataset_id well documented but name only given a type and minLength. The description adds the useful context that the tool removes an 'attribute', which helps map the name parameter to an attribute name, but it does not fully compensate for the missing schema-level description of 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 a specific action ('Remove an attribute') applied to a specific resource ('CityObjects with cjio'). It is distinguishable from the sibling cityjson_attribute_rename, though it does not explicitly name 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?
No guidance is given about when to prefer this tool over alternatives such as cityjson_attribute_rename or other transformation tools. The description does not mention prerequisites, effects, or operation context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.