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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful scoping context ("tenant-configured", "accessible locations" implying permission-limited results), but says nothing about what the summary contains or how results are shaped.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the gaps in parameter and usage guidance rather than reflecting well-judged economy.

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?

No output schema exists, yet the description never indicates what the summary contains (per-location counts, coverage percentages, gap lists) or how the `state` filter interacts with `locationIds`. For a comparative analytics tool with four annotations but zero parameter documentation, more disclosure was needed.

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%, so the description carries full burden. It only vaguely alludes to locations and never mentions the `state` parameter, the UUID format for locationIds, or the 50-item cap, leaving both parameters semantically thin.

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 specific verb ("compare") and specific resources ("credential coverage and training gaps") scoped to "accessible locations", so the core operation is clear. However, it offers no differentiation from the many closely related siblings such as get_location_compliance_analytics, get_site_compliance_analytics, get_compliance_distribution, or get_training_gaps, all of which sound like they could return similar data.

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 explicit when-to-use guidance, no exclusions, and no named alternative. The phrase "across accessible locations" weakly implies a cross-location rollup, but with five near-identical compliance/training siblings, an agent has to guess which one to call.

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