modx_get_access_policy_template

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

With no annotations supplied, the description carries the full behavioral burden and does almost nothing with it. 'Get' implies a read, but it never states that the operation is non-mutating, what happens when the id does not exist, or what permissions are required.

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 no filler and the key qualifier ('by id') placed at the end where it is immediately visible. It is efficient, though its brevity stems partly from omission rather than disciplined editing.

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 one-parameter lookup with no annotations and no output schema, the description should at least sketch the returned object or failure behavior. As written, an agent knows only the name and the lookup key, leaving return shape and error handling entirely unknown.

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% and the single parameter is a bare number. The description only says 'by id', which identifies the parameter's role but adds nothing about format, accepted ranges, or whether the id refers to a template record versus a policy record.

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 ('Get') and a specific resource ('access policy template') qualified by lookup key ('by id'), so an agent knows exactly what it retrieves. It stops short of distinguishing itself from close siblings such as modx_list_access_policy_templates or modx_get_access_policy, which would require a mention of singular-vs-collection or template-vs-policy scope.

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 and no reference to alternatives. The phrase 'by id' weakly implies the tool is for the case where an identifier is already known (versus listing templates to discover them), but that inference is left entirely to the agent.

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