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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds non-obvious return scope: 'including inactive ones' for appointment types, doors' 'own type limits and own hours,' and 'upcoming closures' — details an agent cannot get from the annotations or schema. It is a single-read aggregate ('in one call'), which is useful behavioral context.

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?

It is one dense sentence, but it is front-loaded with the payoff ('Everything about how a location is set up, in one call') before the semicolon-delimited inventory. The enumerated groups all earn their place. The run-on density keeps it just short of a 5.

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?

There is no output schema, so the description must carry the return-value burden — and it does, listing each block of data returned. Combined with annotations covering safety and usage guidance covering timing, an agent has what it needs to call this 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% and the description never mentions the locationId parameter by name or specifies its format (ID vs slug). The single required locationId is semantically self-evident from the tool name and the phrase 'how a location is set up,' so the risk is low, but the description does not compensate for the coverage gap as the rules require for low-coverage schemas.

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 specific verb+resource (get/read the full setup of a location) and enumerates exactly which data is returned: name/address/timezone, scheduling settings, weekly hours, appointment types, doors, and closures. This clearly separates it from list-shaped siblings such as list_locations or list_doors. It stops short of naming an alternative sibling, so it lands at 4 rather than 5.

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?

It gives two concrete invocation contexts: 'Read this before changing setup' and 'when diagnosing missing times.' That is real when-to-use guidance rather than implication. However, it names no explicit alternative (e.g. get_availability or list_doors) or exclusion, so it is not a full 5.

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