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

Annotations already fully declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description earns credit only for the additive data-scope disclosure: metadata/approved fields only, no secrets/contacts/original files. That redaction boundary is genuinely useful. However, it says nothing about what the returned distribution looks like or how limit/offset paginate it, which matters since there is no output schema.

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 tight sentences with no padding, and the read-authorisation plus redaction constraint is front-loaded. It is efficient; the problem is that what remains is under-specified rather than verbose.

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?

Three undocumented parameters, no output schema, and an undefined core concept ("distribution"). An agent could invoke it but could not predict the response shape or whether its `query` was applied correctly—significant gaps for a tool whose only structured documentation is bare types.

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% for all three parameters, so the description carries the full burden — but it mentions none of them. An agent gets no guidance on what `query` matches against (name, credential type, location?) or how limit/offset interact with the 25000 offset cap.

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?

Names a verb (Read) and a resource (compliance distribution), but "distribution" is never defined — distribution of what (credential status counts? compliance percentages?) and at what dimension (employee, location, site)? It also fails to distinguish itself from the many compliance-shaped siblings such as get_compliance_trend, get_copliancy_summary, get_location_compliance_summary, and get_employee_compliance_status.

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?

"through the existing application" is the only hint about context, and it doesn't say when an agent should pick this over get_compliance_trend or get_compliance_distribution vs get_copliancy_summary. No alternatives, no exclusions, no prerequisites are stated anywhere.

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