modx_list_access_policy_templates

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about pagination, ordering, filtering behavior, or read-only semantics. The presence of limit/start parameters hints at paging, but the description never confirms or explains it.

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?

The single sentence is front-loaded and contains no filler, but its brevity comes from omission rather than efficiency; nothing is wasted because almost nothing is said.

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 paginated, filterable list tool with three undocumented parameters, no annotations, and no output schema, the definition leaves the agent guessing about input formats and return shape. It needs at least pagination and filter semantics to be callable with confidence.

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 adds no meaning at all — a caller cannot tell from either source whether query is a substring match, a name filter, or something else.

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?

"List access policy templates" gives a verb and a resource, but it is essentially the tool name with underscores removed — no scope, no explanation of what a policy template is, and no explicit contrast with the nearby modx_list_access_policies.

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 when-to-use guidance, no mention of how this differs from list_access_policies or get_access_policy_template, and no prerequisites such as permissions or context needed to enumerate templates.

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