modx_virtualpage_list_handlers

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: not whether it is read-only, whether results are paginated, what the default limit is, or whether the optionally included routes make the call heavier. 'List' implies a read, but that is inference rather than disclosure.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is partly the cause of the gaps in the other dimensions rather than a virtue in itself.

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 tool with 8 entirely undocumented parameters, no annotations, and no output schema, one sentence is not sufficient. The agent learns what it lists but not how to filter it, what it returns, or how to page through results.

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 8 parameters, including opaque ones like 'entry', 'type', 'active', and 'include_routes', and the description explains none of them. The phrase about rendering resources/snippets/chunks hints at a handler-type concept but never maps it to the 'type' or 'entry' parameters, leaving the agent to guess.

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 pairs a specific verb ('List') with a specific resource ('VirtualPage handlers') and adds scope ('that render resources, snippets, chunks, or dynamic resources'), which is enough to distinguish it from get_handler and the create/update/delete handler siblings. It stops short of naming those siblings explicitly, so it is clear rather than fully differentiating.

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 statement of when to call this instead of modx_virtualpage_get_handler, modx_virtualpage_list_routes, or modx_virtualpage_list_events. A user must infer that this is the enumeration tool for handlers; nothing addresses exclusions, prerequisites, or filtering workflows.

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