get_location

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

No annotations are provided, so the description must carry the behavioral disclosure burden. The verb 'fetch' implies a read-only operation, but the description provides no additional behavioral traits such as return format, error behavior, permissions, or side effects. It is minimally adequate but lacks depth.

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 a single short sentence that is front-loaded and directly states the tool's purpose. There is zero wasted text or redundancy.

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 simple one-parameter getter, the description plus schema are largely complete. However, it could mention that get_locations is the alternative for fetching multiple locations, and it doesn't describe the output shape (though no output schema exists). Still, given the tool's simplicity, the coverage is 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?

The input schema provides 100% coverage for the single parameter 'id' with a helpful example ('gid://shopify/Location/123456789'). The description adds no additional semantic meaning beyond restating that it fetches by ID, so the schema does the heavy lifting.

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 'Fetch a specific location by ID' uses a specific verb ('fetch') and resource ('location') and clearly identifies the selector (by ID). It distinguishes from sibling tools like get_locations (plural) and other location-related operations.

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 implies usage when a specific location ID is known, but it doesn't explicitly mention alternatives such as get_locations for listing all locations, or contrast with create/update/delete location tools. There is no when-not-to-use guidance.

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