list_personnel_with_issues

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. It clarifies what 'issues' means (failing device compliance) but says nothing about scope (tenant-wide? all personnel?), pagination or result limits, whether personnel with zero enrolled devices are included, or any auth context for an access-control dataset. For a tool with zero annotation coverage this is a notable gap.

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?

Two short, front-loaded lines with no filler, and the qualification '(failing devices)' is placed immediately after the term it disambiguates. The 'Returns:' line largely restates the first sentence and duplicates what the existing output schema already conveys, which is the only (minor) waste.

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?

An output schema exists, so return structure needn't be described, and a zero-parameter tool is inherently simple. Still, with no annotations the description should have covered scope, pagination/limits, and whether the list is tenant-wide; those omissions leave an agent slightly unsure what the result set represents.

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?

The tool takes no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds nothing about inputs, which is consistent with the empty schema.

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 uses a clear verb+resource+qualifier: get personnel filtered to those with compliance issues, and it defines the qualifier as '(failing devices)'. It does not explicitly name the sibling it contrasts with (e.g. list_personnel for the unfiltered list, or list_failing_monitors for the device-level view), so sibling differentiation is only implied rather than stated.

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?

Usage is implied: an agent can infer this is the filtered counterpart to list_personnel and that it should be chosen when the question is 'who has a compliance problem'. There is no explicit when-to-use/when-not-to-use statement and no alternative tool is named, which is why this stays at minimum-viable rather than 4.

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