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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully structured. The description adds nothing beyond that profile – no pagination behavior, no result ordering, no note about whether unassigned sites return an empty list.

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, but its brevity is under-specification rather than economy – nothing about pagination or scope is included even though the schema leaves it undocumented.

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 and annotations carry the safety profile, so return values and read semantics needn't be restated. But for a paginated list endpoint with 0% parameter documentation, the description leaves material gaps: default/max page size and the ambiguous term 'site' versus locationId.

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. 'Site' weakly maps to locationId, but limit and offset (default 25, max 100 / max 10000) are never mentioned, so an agent could silently truncate results without knowing pagination exists.

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?

States a specific verb ('Read') and resource ('policies assigned to a site'), which is enough to distinguish it from get_policy or list_policies. However, it never names or contrasts with the closest siblings, list_policy_assignments and get_policy_assignment, so the boundary is left to inference.

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 prefer this over list_policies, list_policy_assignments, or get_location_compliance_gaps. No prerequisites, no exclusions, no alternative routing.

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