get_commander_status

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

No annotations are provided, so the description carries the full burden, and 'from local journals' is the only behavioral clue (data source). It says nothing about read-only safety, auth/permission needs, staleness of local journal data, or what happens when journals are absent.

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-fragment with no filler, front-loading the returned fields. It is efficient, though its fragmentary style contributes to the missing verb/action.

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 return values needn't be explained, but the one input parameter is entirely undocumented and there is zero usage context. For an aggregate status tool with many overlapping siblings, this leaves notable gaps.

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 description coverage is 0% for the single 'journal_dir' parameter, and the description never mentions it, so the agent gets no help on what directory it expects, its format, or its default-null behavior. With one undocumented parameter this falls below the 3 baseline that a fully covered schema would earn.

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 enumerates the returned fields (commander name, system/station, ship, credits) but never states a verb or action, reading as a noun phrase rather than a description of an operation. It gives a partial sense of scope versus siblings like get_current_location or get_ship_loadout, but doesn't explicitly frame itself as an aggregate status snapshot.

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?

There is no when-to-use guidance, no mention of alternatives among the many location/ship/inara sibling tools, and no exclusions. The agent is left to infer that this is a broad status read versus the narrower siblings.

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