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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful data-scope context ('metadata/approved fields only; no secrets, contacts or original files'), but it does not describe pagination behavior, return format, or authorization requirements beyond 'authorised'.

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 two sentences and front-loads the purpose before the data-scope qualifier. There is minor filler ('through the existing application'), but overall it is tight and appropriately sized for the tool.

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 low-complexity read-only analytics tool with rich annotations, the description covers the general purpose and data scope. However, it leaves parameter semantics unexplained and fails to differentiate this from the many sibling analytics tools, and with no output schema it could say more about the shape of the returned analytics.

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 (limit, query, offset), and the description provides no information about them. It does not explain what 'query' searches, how limit/offset behave, or what constraints apply, leaving an agent with bare schema types and defaults only.

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 states a clear verb and resource: 'Read authorised site compliance analytics,' and adds a data-scope qualifier. However, it does not distinguish this tool from numerous analytics siblings such as get_location_compliance_analytics or get_compliance_distribution, and the meaning of 'site' versus 'location' is left ambiguous.

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 use this tool versus alternatives, no prerequisites, and no exclusions. 'Metadata/approved fields only' describes data scope, not when the tool should be selected over sibling analytics tools.

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