materials_remove_property

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

No annotations are provided, so the description carries the full behavioral burden. It implies a destructive edit via 'Remove entries', but says nothing about persistence, whether the file is rewritten in place, reversibility, or what happens when no entry matches.

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?

A single tight sentence with the action front-loaded and no padding. It could be slightly clearer by separating the file argument from the filters, but nothing is wasted.

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?

An output schema exists so return values need not be explained, but for a mutation tool with zero annotation coverage and 0% parameter documentation, the description should say more about failure modes (no match, missing file) and side effects on the resulting Materials.json.

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 0%, so the description must compensate and it partly does: it clarifies that model_part_name and properties_id are optional filters combined with AND semantics ('all given criteria must match'). However it says nothing about the required materials_file parameter's format or path expectations.

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?

States a specific verb (remove), resource (entries in Materials.json) and the matching criteria, so an agent immediately understands it edits a materials file. It is distinguishable from siblings like materials_set_property and materials_get, though it never names them explicitly.

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 explains the matching rule but gives no when-to-use context, no alternative tool to prefer for related edits, and no prerequisites (e.g., file must already exist, whether a validation pass like materials_check should precede it).

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