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

The annotations already declare this as a safe read-only, idempotent, non-destructive, closed-world operation, so the behavioral bar is lower. The description adds the specific gap categories it surfaces, but does not explain pagination, result ordering, or any permission constraints beyond what annotations cover.

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 description is a single front-loaded sentence with no wasted words. It is appropriately sized, though its brevity contributes to gaps in other dimensions rather than being a flaw in conciseness 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?

Given four undocumented filter parameters, no output schema, and a closely related sibling tool, the description is too thin to fully equip an agent. It explains what categories of gaps are found but not how to filter, paginate, or interpret 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?

The schema has 4 parameters with 0% description coverage, and the description does not mention limit, offset, state, or locationIds at all. It only references 'state-matrix' as part of a gap category, which does not clarify the state filter parameter.

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 names a clear verb (Find) and specifies the resource and the gap categories (incomplete, overdue, inactive, missing job-title/state-matrix credential assignments). It is specific enough for an agent to know what the tool returns, but it does not differentiate it from the very similar sibling review_training_gaps.

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 guidance on when to choose this tool over alternatives such as review_training_gaps or list_overdue_credentials. The description gives no prerequisites, exclusions, or context for selection, leaving the agent to infer usage.

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