esri_wayback

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Every historical imagery version since 2014' gives a useful coverage/currency fact, but nothing about whether this is a static catalog, whether results are paginated or cached, permission requirements, or latency — significant gaps for a tool with zero annotation coverage.

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?

A single compact sentence with no filler. The 'time-travel manifest' framing is slightly decorative, but the substantive content (ESRI, Wayback, historical versions, since 2014) is front-loaded and immediately readable.

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?

An output schema exists, so return values needn't be explained, and zero params means the calling surface is trivially simple. What's missing is ecosystem context: how this connects to aoi_imagery or history_diff, which is the main thing an agent needs to invoke it at the right moment.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly avoids inventing parameter-like detail that doesn't exist.

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 identifies the resource (an ESRI Wayback manifest of historical imagery versions since 2014) but has no verb, so it's unclear whether the tool returns a catalog list, fetches a specific version, or does something else. It also doesn't distinguish itself from imagery-adjacent siblings like aoi_imagery, sar_scenes, or history_diff.

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 guidance on when to call this versus alternatives. Nothing says whether it's a discovery step meant to feed aoi_imagery, or whether it should be used standalone — the agent must guess from the sibling list.

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