list_tours

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

No annotations are provided, so the description carries the full behavioral burden. It signals a read/list operation and notes that limit is the max number of tours to return, but omits authentication requirements, pagination behavior, sort order, and whether filters combine.

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?

The description is front-loaded with the purpose, then uses a compact Args list for parameter details. Every sentence contributes either usage or parameter meaning, with no filler or repetition beyond useful clarification.

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 covers all parameters and the output schema handles return values, which is helpful. With no annotations and six optional parameters, however, missing auth expectations, pagination behavior, and read-only confirmation leave some gaps for correct invocation.

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%, so the description must compensate, and it documents all six parameters. It adds useful examples for sport_type and tour_type and explains the relationship between near_lat, near_lon, and radius_km, though it does not restate schema defaults.

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 the specific verb 'List' and resource 'Komoot tours', with optional filters, so the core operation is clear. It does not explicitly distinguish this tool from siblings such as get_tour_details, but the listing purpose is unmistakable from the name and description.

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?

Provides practical filtering guidance, including how to use near_lat/near_lon for geographic search and radius_km with them. However, it does not say when to choose this tool over alternatives like get_tour_details or get_highlights, leaving usage context largely implied.

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