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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the phrase 'sharing metadata', which hints at returned content but says nothing about pagination behavior, ordering, or what sharing fields appear — nothing beyond the annotations.

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 short, front-loaded sentence with no filler. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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, so return values need not be explained, and annotations cover safety. But for a tool sitting among a dozen similar list_location_* siblings, the description does not give enough context for an agent to choose this one confidently or to page results correctly.

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 three parameters (locationId, limit, offset). The word 'site' weakly implies the locationId scope, but the description never mentions limit/offset or the default page size of 25 and max of 100, so an agent gets no help on pagination semantics — a meaningful gap at 0% coverage.

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 verb ('List') and an object ('site files and sharing metadata'), which roughly maps to location documents. However, with close siblings such as list_location_resources, list_location_books, list_location_policies and list_field_attachments, the description gives no basis for telling them apart — what counts as a "document" here versus a resource or a book 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 use this tool versus the many other list_location_* siblings, nor on prerequisites or follow-up actions (e.g. that download_location_document is the companion tool for fetching content). Usage must be inferred entirely from the name.

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