list_tours

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

No annotations are provided, so the description must fully disclose behavioral traits. It only lists parameters and does not mention pagination behavior, sorting details, authentication needs, or any side effects. The description is essentially a parameter list without additional behavioral context.

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 concise, front-loaded with the purpose, and structured as a clear argument list. It contains no unnecessary text, though it could be slightly more streamlined.

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?

Given the 8 optional parameters and existence of an output schema, the description covers parameter semantics adequately but lacks behavioral context such as default sort order or pagination behavior. It is complete for a parameter list but missing some operational context.

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 compensates by explaining each parameter with examples and constraints (e.g., tour_type: 'tour_planned', 'tour_recorded', or None; sport_types: comma-separated; page: 0-indexed; limit: default 30, max 100). This adds significant meaning beyond the bare schema.

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 'List your Komoot tours (planned and recorded).' It specifies the verb 'list' and the resource 'tours', distinguishing it from sibling tools like get_tour (single tour) or plan_route.

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 does not provide explicit guidance on when to use this tool versus alternatives such as get_tour for a single tour or create_planned_tour for creation. It implies that listing is for multiple tours but lacks explicit when/when-not instructions.

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