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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the meaningful behavioral note that it renders an interactive grid, but says nothing about pagination behavior (limit/offset), result contents, or accessibility filtering beyond the word "accessible".

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?

Two tight sentences with the capability stated first and the usage cue second. Nothing is redundant or padded.

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, 0% parameter coverage, and no sibling differentiation, the description is too thin to call the tool correctly. It should at minimum explain the kinds filter, pagination via limit/offset, and how it differs from geobble_search.

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 0% for all four parameters, so the schema names them (kinds, limit, query, offset) without explaining any of them. The description contributes zero parameter detail, leaving the kinds enum, the 12/50 limit bounds, and offset-based paging entirely unexplained.

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 (Search) and resource (accessible Geobble resources) and adds the distinctive behavior of rendering an interactive result grid. It is clear what the tool does, but it never names the sibling geobble_search, so the agent must infer the visual-vs-plain distinction itself.

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?

"Use when visual selection would help the user" gives an implied usage context, but there is no explicit when-not guidance and no named alternative (e.g. geobble_search) to route between. The agent must infer the tradeoff on its own.

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