modx_list_property_sets

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, and it only enumerates returned fields. It says nothing about pagination (limit/start), whether 'query' filters by name, default page size, ordering, or permission requirements for reading property sets.

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 compact sentence, front-loaded with the verb and resource, with no filler. It is efficient, but its brevity comes partly from omitting information rather than from careful compression.

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 list tool with three undocumented parameters, no annotations, and no output schema, the description should explain pagination and filtering. Enumerating the returned fields partly compensates for the missing output schema, but the call mechanics remain unspecified.

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?

All three parameters (limit, query, start) have 0% schema description coverage, and the description never mentions them. It does not say what 'query' matches against or how limit and start interact, so the agent must guess at conventional meanings.

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 ('List') and resource ('property sets'), plus the underlying class name modPropertySet and the fields returned (id, name, description, category). That is enough to distinguish it from modx_get_property_set or modx_create_property_set, though it never states the distinction 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?

There is no guidance on when to use this instead of modx_get_property_set or the create/update/delete siblings, and no prerequisites or exclusions. The 'List' verb implies the multi-record case, but the agent has to infer that on its own.

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