Gbp.Location.Get

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

No annotations are provided, so the description carries the full burden. 'Fetch' implies a read, but it does not disclose what happens on an unknown location name, whether permissions/account access are required, or that 'resource name' must be the full accounts/{id}/locations/{id} form rather than a bare ID.

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?

One front-loaded sentence with no filler or repetition. It is efficient, though its brevity is also the source of the missing guidance rather than a deliberate trade-off.

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 described. However, with no annotations and zero schema description coverage, an agent still lacks the identifier format and error/permission behavior needed to invoke this reliably.

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 single parameter has no description in the schema, so the description must compensate. Saying 'by resource name' does add meaning over the bare property name location_name, hinting at the identifier format, but it never spells out the format or an example.

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 (Fetch) and resource (a single GBP location's details), and the word 'single' implicitly distinguishes it from the sibling gbp.locations.list. It does not explicitly name that sibling or other alternatives, but the purpose is unambiguous.

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 only implied: an agent can infer you call this when you already have one location's resource name. There is no explicit statement of when to prefer this over gbp.locations.list, nor any prerequisite (e.g., needing the resource name from a list call first).

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