create_planned_tour

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

No annotations provided. Description only indicates a create operation but does not mention side effects, permissions, required auth, or behavior on invalid input. Lacks depth beyond the action.

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?

Short and structured with an Args block. No unnecessary words, but could integrate Args more naturally. Front-loaded with purpose.

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?

Has output schema, so return values are covered. Lacks prerequisites (e.g., valid route_data), error handling, or idempotency info. Adequate for a simple creation tool.

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 has 0% description coverage. Description adds meaning for route_data (JSON from specific tools) but only minimal for name and sport (defaults not stated). Compensates partially, not fully.

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?

Description states verb 'create' and resource 'planned tour on Komoot', and specifies input sources (plan_route or import_gpx_route outputs). It distinguishes from siblings like plan_route and import_gpx_route by clarifying its role as a post-processing step.

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?

Implicitly indicates usage after plan_route or import_gpx_route, but no explicit when-not or alternatives. Could be more direct about prerequisites.

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