Get current location

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

readOnlyHint=true already covers the safety profile, but the description adds genuinely useful provenance: the value is the last one set via set_current_location, not a live GPS fix, so an agent can reason about staleness. It omits what happens when no location has ever been set (null? error?), which keeps this below a 5.

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?

A single front-loaded sentence with no filler; the return semantics lead and the provenance caveat follows immediately. Every clause carries 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, the description should say what shape the answer takes (coordinates, place object, place name) and what is returned when no location is set. It covers only the conceptual return value, leaving the agent to discover the payload structure at call time.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add. Nothing in the schema is left unexplained.

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?

"Returns where the user currently is" gives a specific verb plus resource, and the parenthetical ties it to set_current_location, so the agent can tell it apart from the write-side sibling. It stops short of distinguishing it from read siblings like list_places or search_address, which also surface location data.

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: fetch the user's present position when needed. There is no explicit when-to-use or when-not-to-use guidance, and no mention of preferring list_places for saved locations or search_address for lookups.

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