prtg_groups

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

The '[READ]' tag merely restates the readOnlyHint=true annotation, adding no new information. No mention of return volume, pagination, ordering, or whether the default target vs. a named target behaves differently. With annotations covering only the safety profile, the description leaves the behavioral picture thin.

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 front-loaded sentence stating purpose, then a compact Args block. No filler, though the '[READ]' prefix is redundant with the annotation and could be dropped.

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 single-param read-only list tool with no output schema, the core purpose and the parameter semantics are covered. Still missing is any notion of what a group record contains beyond 'rollup status' or how results are ordered, which would help an agent consume the output.

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 coverage is 0% – the schema gives only a nullable string titled 'Target' with default null. The description supplies the missing meaning: it is a 'PRTG target name from config' and omitting it selects the default. That compensates for the coverage gap, though it doesn't explain what valid target names look like.

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 clear verb+resource: 'List PRTG device groups' plus the distinguishing scope 'with their rollup status'. The resource (groups) separates it from siblings like prtg_devices and prtg_sensors, though the description never names those siblings to make the routing explicit.

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?

No guidance on when to use this versus prtg_devices, prtg_sensors, or prtg_sensor_details, all of which return related PRTG hierarchy data. The only usage note is that target may be omitted, which is a parameter detail rather than tool-selection guidance.

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