modx_unassign_property_set

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

No annotations are provided, so the description carries the full disclosure burden. For a mutation tool it says nothing about permissions required, reversibility, what exactly is unlinked versus deleted, or what happens to an element's existing bindings — only that a property set is detached.

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 short sentence with the verb and target front-loaded; nothing is padded. The parenthetical is efficient, though the brevity comes at the cost of missing detail rather than being crisply informative.

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 four-parameter mutation with no annotations, no output schema, and zero parameter documentation, so the description needs to do more work. Delegating identification semantics to another tool leaves an agent guessing at core call correctness.

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% across four parameters, and the description only says identification 'same as assign' rather than explaining it. It never clarifies whether 'element' and 'property_set' are numeric IDs, what 'element_class' means relative to 'element_type', or when the optional parameters are needed.

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 and resource: 'Detach a property set from an element'. It also ties itself to the sibling modx_assign_property_set via 'same identification as assign', so an agent can distinguish it from the assign tool. It stops short of naming the assign sibling outright as the 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?

Usage is only implied by the word 'Detach' and the parenthetical reference back to the assign tool. There is no explicit when-to-use vs. modx_assign_property_set or modx_delete_property_set, and no statement about prerequisites or whether the property set itself survives the detachment.

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