Get a location

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint true, and destructiveHint false, so the safety profile is clear. The description adds useful behavioral context about the API version, path naming convention, and that the readMask controls which fields are returned, which goes beyond the annotations.

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 two sentences and directly states the core purpose, followed by a useful list of field options. It is front-loaded with the primary action and avoids irrelevant details, earning its place.

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?

Given the tool's simplicity and the rich parameter descriptions in the schema, the description is adequately complete. It explains the API version, return a single location, and how readMask influences output. There's no output schema, but the description plus schema sufficiently cover what's needed for invocation.

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 both parameters have descriptions. The description adds extra value by enumerating all possible readMask field choices (title, categories, etc.) and clarifying the acceptable formats for locationId, complementing the schema's example. This goes beyond what the schema alone provides.

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 clearly states 'Returns one location by id', specifying the exact resource and operation. It also distinguishes from sibling tools like list_locations and get_review by indicating it's a single-location lookup within the Business Information API.

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 description provides clear context for when to use this tool (fetching a single location by ID) and includes a subtle usage note about v1's bare path name. However, it does not explicitly mention alternatives or when not to use it, though the context implies it for single-location retrieval.

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