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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), and the description reinforces it with 'It only reads, so it never asks for your OK.' More valuably, it discloses behavior not in the annotations: the download link expires after 1 hour and the call requires the user's Cotlet API key with access to the app.

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?

Purpose is front-loaded, but the 'valid for 1 hour' fact is stated twice in the first two sentences, which is wasted repetition. Otherwise dense and readable, no filler beyond that duplication.

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?

With no output schema, the description carries the return-value burden and does so: download link, validity window, and the media zip contents. Auth requirements and format contents are also covered. Minor gap is the absence of any file-size or post-expiry guidance, but nothing essential to invoking correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: what each format contains (gpx=route, markdown=step stories) and what include_media produces (a zip of full-size photos and videos). That goes beyond the terse schema 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 gives a precise verb and resource: 'Exports one trip as json, gpx or markdown and returns a download link'. This inherently distinguishes it from the sibling get_trip/list_trips (which return data inline rather than a download link). It stops short of explicitly naming an alternative, so it lands at 4 rather than 5.

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?

There is no explicit when-to-use or when-not phrasing. The closest is the format guidance ('gpx holds the route, markdown holds the step stories'), which implies selection criteria between formats but leaves the choice of export-vs-get to inference.

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