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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: it is keyless, licensed CC BY-SA, returns full-size and thumbnail JPEG URLs, and hints at pagination through the example. It stops short of stating rate limits or ordering guarantees across pages.

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?

Front-loads the core purpose, then usage, licensing, and example in a logical order with no filler. The long field enumeration is dense but earns its place given there is no output schema.

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 usefully enumerates exactly what is returned (position, heading, timestamp, GPS accuracy, OSM way match, JPEG URLs). Combined with the usage routing and licensing note, an agent has everything needed to call and interpret this 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 coverage is 100% and both limit and offset are documented with ranges and defaults in the schema, so the description need not carry that burden. The embedded example call duplicates the schema's own examples field rather than adding new semantic meaning to the parameters.

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 a specific verb (return every frame) and resource (one KartaView drive) plus scope (capture order) and enumerates the fields returned. It is clearly separable from kartaview_nearby_sequences, which is point-based rather than drive-based.

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?

Explicitly says when to use it ('Use after kartaview_nearby_sequences to follow a street rather than stand at one point'), naming the sibling and the condition that selects this tool over it. No inference required.

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