Get hideout station

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

With no annotations, the description must carry the behavioral burden. It discloses that output includes construction times, required items, trader loyalty, and required stations, plus the notable behavior that 'Item/station ids are resolved to names.' It does not mention error behavior or explicitly confirm read-only status, but 'get' implies no side effects.

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?

Two sentences with no fluff. The core purpose and selection method are front-loaded, followed by a concise list of included details and a behavioral note. Every sentence earns its place.

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?

The description adequately explains what data will be returned for a single-station lookup, even without an output schema. It does not cover edge cases like 'not found' behavior, but for a simple get-by-id/name tool, the provided detail is largely sufficient.

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 100%, so the baseline is 3. The description adds value by clarifying that idOrName accepts either an ID or a name and by highlighting that IDs are resolved to names in the output, which helps agents understand parameter behavior.

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 states a specific verb and resource: 'Get full detail for one hideout station by id or name' and enumerates the contained data. It clearly differentiates from the sibling list_hideout_stations by emphasizing 'one' and 'full detail'.

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 usage context is clear: this tool is for retrieving a single hideout station's detailed informationtons, while list_hideout_stations exists for enumeration. However, it does not explicitly name the alternative or state when not to use this tool, which would merit a 5.

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