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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value beyond them by disclosing the returned field set (name, address, phone, website, time zone, POS merchant id) and the underlying endpoint GET /locations/{location_uuid}, which is useful given there is no output schema.

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 telegraphic clauses with no filler: the resource and return fields come first, the endpoint mapping second. Every fragment carries information an agent can use.

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 single-parameter read tool with no output schema, the description compensates by listing the returned fields and citing the endpoint, and annotations cover the safety profile. It is nearly complete, though a note on what happens for an unknown uuid (error vs empty) is absent.

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?

There is only one parameter with 100% schema description coverage, including the pattern and a pointer to homebase_list_locations as the source. The description's 'by uuid' adds no semantics beyond what the schema already states, so the baseline of 3 applies.

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 ('Get') and resource ('one location by uuid') and enumerates the returned fields, which cleanly separates it from the plural homebase_list_locations. It does not explicitly name siblings like homebase_get_location_plan, so differentiation relies on inference from the singular 'one location'.

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?

The phrase 'by uuid' implies the prerequisite of already having a location uuid, which the schema confirms comes from homebase_list_locations. However, there is no explicit when-to-use guidance or any statement about when to prefer this over homebase_list_locations or homebase_get_location_plan.

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