get_current_location

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

With no annotations provided, the description must carry the behavioral burden, and it does disclose the provenance (latest Location/FSDJump/Docked event), which tells the agent the result reflects the most recent relevant journal entry. However, it says nothing about read-only nature, failure modes when no event exists, or staleness behavior.

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 compact sentence with no filler, front-loading the returned data and its source. It leans toward under-specification rather than verbosity, but every word 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?

An output schema exists, so the terse description needn't enumerate return fields. Yet the undocumented journal_dir parameter and absent failure/empty-state behavior leave gaps for an agent calling the tool without prior knowledge.

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 single parameter journal_dir has 0% schema description coverage, and the description never mentions it. An agent cannot tell whether journal_dir is required, what format it takes, or what the default behavior is when omitted.

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 resource (current system, coordinates, station) and the data source it derives from, so an agent immediately knows this returns the player's present position. It is distinguishable from siblings like get_ship_loadout or get_commander_status, though the terse phrasing leaves the exact field set to the output schema.

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 names the underlying journal events but gives no guidance on when to call this versus alternatives such as get_journal_history or get_commander_status. No prerequisites (e.g., needing a journal_dir or prior game session) are mentioned.

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