Export Dawarich track

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that it 'downloads' one journey and returns in multiple formats, which is useful but not deep behavioral context. It does not mention size limits, pagination, or what 'summary' entails, but with annotations present, a score of 3 is appropriate.

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 a single, front-loaded sentence. It states the action, scope, and output formats without any filler or repetition. Every word contributes to understanding the tool's core function.

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 tool's simplicity and the rich schema with 100% parameter coverage, the description sufficiently conveys the return value formats. It doesn't explain the content of 'summary' or exact CSV structure, but for an export tool with clear format options, this is largely 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 description coverage is 100%, with both parameters having descriptive text. The description reinforces that a single journey is exported, which matches track_id semantics, but it does not add significant meaning beyond the schema's existing property descriptions.

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 identifies the action ('Downloads one Dawarich journey') and the resource ('Dawarich journey'), and specifies output formats (compact JSON, GeoJSON LineString, CSV). It distinguishes itself from sibling tools like dawarich_get_track_points and dawarich_get_track_detail by emphasizing export in multiple formats.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention that this is for exporting complete journeys in structured formats, nor does it exclude other tools. The format options imply use cases but no direct comparison.

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