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

Annotations already establish that this is a safe read-only, idempotent operation. The description adds useful context by detailing the returned business record and explaining that it is the NAP record used for citation and listing comparisons, though it does not discuss not-found behavior or permissions.

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 front-loaded and clear, but the two sentences substantially duplicate the same field list: the first names categories such as name, address, phone, and hours, while the second repeats them with more detail. It could be tightened without losing information.

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?

With no output schema and a single well-documented parameter, the description adequately explains the returned record. It would be more complete with a note on missing or inaccessible locations, but the essential retrieval behavior is covered.

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?

The input schema has 100% description coverage and already explains that location_id comes from list_locations. The description does not add meaning beyond that, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Read one location's business details,' then enumerates the returned fields. It clearly distinguishes this single-record retrieval from the sibling list_locations tool by referring to 'one location' and noting that location_id comes from list_locations.

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?

Usage is implied: use this to retrieve a single location's details, with the ID sourced from list_locations. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives such as list_locations or get_gbp_audit are named for comparison.

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