Entur: finn stoppested

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

No annotations are provided, so the description carries the full burden. It discloses the source and license, which is useful context, and the verb 'Søker' implies a read-only operation. However, it does not mention response format, pagination, or behavior on no results, which would strengthen transparency.

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 concise sentences: the first is front-loaded with the core action and result, the second adds provenance (source and license). No redundant wording, 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?

For a simple search tool with no output schema, the description covers the essential need: what it does and what you get (ID). It could be more complete by explaining parameter usage and possible response behavior, but given the low complexity, it is adequately complete.

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%, so the description must compensate. It explains the tool's overall purpose but does not elaborate on the 'sok' or 'antall' parameters beyond what the schema already shows (name and constraints). The meaning of 'sok' is inferable, but 'antall' is only hinted by the schema's max/min, not described.

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 a specific action ('Søker etter holdeplasser og stasjoner') and resource (stops/stations), with a concrete output (Entur ID needed for departures). It differentiates from sibling tools like entur_avganger (departures) and entur_reise (journeys).

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 implies when to use: you need the Entur ID 'for avganger' (for departures), clearly positioning this as a prerequisite to departure queries. It does not explicitly name alternatives, but the context is enough to guide an agent.

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