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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds essentially nothing beyond that: "in full" hints at a complete representation but never says what fields are returned, what happens for an unknown or archived location, or whether permission scoping applies.

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 very short sentences with zero padding, and the core statement is front-loaded. It is under-specified rather than bloated, which the other dimensions already penalize.

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 one-parameter read tool with a fully described schema and a readOnlyHint annotation, the minimum needed to call it correctly is present. Still, the description offers no return-shape summary (there is no output schema) and no failure-mode context, leaving it only just adequate.

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 coverage is 100% and the single parameter location_id is documented in the schema, so baseline 3 applies. "GET /locations/{id}" only confirms that the id in the path is the location_id — no additional format, range, or sourcing guidance.

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 fragment "One location in full" combined with the name and title makes the resource (a single location) and the single-record scope identifiable, and implicitly contrasts with splose_list_locations. However, it never states an explicit verb like "retrieve" and relies on the name to carry the action, so it sits at vague-but-inferable rather than specific.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative splose_list_locations for browsing multiple locations. The agent must infer everything from the tool name and the sibling list.

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