stations

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

With no annotations, the description carries the full burden and discloses almost nothing: read-only behavior is only implied by 'List', and there is no mention of result volume, ordering, pagination, or what a station record contains.

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 short sentence with no padding, which is appropriately front-loaded. However, the terseness comes at the cost of the details an agent needs, so brevity here reads as under-specification rather than economy.

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?

No annotations, no output schema, and an undocumented parameter mean the description must compensate for all of it, and it does not. Nothing about the hierarchy linking area_level1/area_level2 to area2_id is explained, leaving the calling workflow incomplete.

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 coverage is 0% for the single required parameter, so the description is the only source of meaning. 'Second level area' hints that area2_id refers to a level-2 geographic area, but it gives no format, range, or how to obtain a valid id.

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 verb+resource ('List stations') is specific, but the scope phrase 'second level area' is unexplained jargon that only indirectly maps to the area2_id parameter. An agent can guess this retrieves stations within a level-2 area, but must infer the relationship rather than being told.

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 guidance on when to use this versus siblings such as area_level2, popular_nearby, or tabelog_get, nor any stated prerequisite for obtaining an area2_id. The agent is left to infer the workflow entirely.

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