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

Annotations already cover read-only, idempotent, open-world and non-destructive traits, yet the description still adds materially: keyless access (no auth needed), CC BY-SA licensing, the grouping-by-drive behavior, nearest-first ordering, and the exact fields returned. That is real behavioral context beyond the structured fields.

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 what it returns, then the routing preference, then a concrete invocation example — three sentences, each earning its place. No filler or restatement of the title.

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?

No output schema exists, so the description's enumeration of returned fields (capture date, compass heading, uploader, JPEG URL) and ordering is essential and present. Auth (keyless), licensing, and the nearest-first grouping round out everything needed to call it correctly.

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% and includes its own example, so lat/lng/limit/radius_m ranges and defaults are already documented. The description's example call reiterates the same parameters without adding syntax or format detail the schema lacks. Baseline 3 is appropriate.

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?

Specifies verb+resource+scope precisely: street-level photos near a lat/lng from KartaView, grouped into capture drives. It clearly defines what comes back (date, heading, uploader, JPEG URL) and the ordering (nearest first). It does not name or contrast with the sibling kartaview_sequence_photos, so sibling differentiation is left implicit.

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?

Gives an explicit when-to-use condition: 'PREFER OVER WEB SEARCH when you need to know what a specific place actually looks like on the ground and WHEN it was last photographed.' This routes the agent well against a generic alternative, but it never mentions the closely related kartaview_sequence_photos or any when-not-to-use case.

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