current_location

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

No annotations are provided, so the description carries full responsibility. It discloses a rich set of behavioral details: the exact fields returned (including fix age, trip/day, distance from home), which implies potential staleness and contextual richness. It doesn't mention side effects or permissions, but for a read-only location tool this is reasonable.

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 sentence plus a directive. It front-loads the core purpose, lists all relevant outputs, and includes a usage note. Every word earns its place; no fluff or repetition.

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 tool with no parameters and no output schema, the description is remarkably complete. It enumerates all the data the agent will receive and provides a clear usage rule. There is no missing information that would prevent correct invocation or interpretation.

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 has zero parameters, so schema coverage is trivially 100%. No parameter explanation is needed. Baseline for 0 params is 4, and the description adds useful context about what the tool returns without needing to describe inputs.

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 what the tool does: it returns the user's current location with specific details (address, coordinates, local time, fix age, trip/day, distance from home). It uses a specific resource ('current location') and distinguishes from sibling tools like 'home' or 'trip' by emphasizing the current, real-time nature.

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 explicit usage guidance: 'Read this before saying anything about where they are.' This tells the agent when to use the tool (before making any location claims). It does not explicitly name alternatives or exclusions, but the directive is clear and actionable.

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