modx_delete_property_set

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

With no annotations supplied, the description carries the full burden of behavioral disclosure, and it only implies mutation through the word "Delete." It says nothing about permanence, whether assignments to elements are cleaned up, what permission level is required, or what a successful response contains. For a destructive tool this leaves the most consequential traits undisclosed.

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?

One short sentence with the action front-loaded and no filler. It is efficient, though the brevity is underspecification rather than disciplined conciseness given everything left unsaid.

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?

The tool is simple in shape (one required param, no nested objects, no output schema), but it is a destructive mutation with zero annotation coverage and no parameter documentation. The description does not close any of those gaps, so an agent cannot judge the blast radius of the call.

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 for the single undocumented parameter. "by id" merely echoes the parameter name and adds no format, type, or sourcing detail (e.g., whether the id comes from modx_list_property_sets) that would help an agent supply a valid value.

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 gives a specific verb plus resource ("Delete a property set") and names the identifier used, so an agent knows exactly what resource is being removed. It does not, however, distinguish this from neighboring operations such as modx_unassign_property_set or reference the list/get/create/update siblings, so the differentiation work is left to the tool name.

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?

There is no guidance on when to use this versus modx_unassign_property_set (detach from an element) or modx_update_property_set (modify in place). No prerequisites, no warning that the operation is irreversible, and no indication of what happens to elements that had the set assigned.

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