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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that only *published* objects are returned, a genuine filtering behavior. It omits pagination/result-size behavior and whether out-of-range viewports error, so it adds modest value over the annotations.

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 front-loaded sentence naming the action first, then the prerequisite. Zero waste, though it is arguably too terse given the parameter burden it is asked to carry.

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-value documentation is rightly omitted. But for a 6-required-parameter spatial query with no schema descriptions, the absence of coordinate-system, zoom, and viewport-boundary semantics leaves meaningful gaps for correct invocation.

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% across 6 required parameters, so the description must compensate and largely does not. It implies the four bounding coordinates via 'viewport' and explains where map_id comes from, but says nothing about zoom, coordinate units, or ordering conventions. Two of six parameters effectively have no semantic guidance anywhere.

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+resource: returning published objects scoped to a viewport. It also names the data source dependency (map_id from list_maps), which separates it from siblings like list_maps and search_topics. It stops short of explicitly contrasting with search_topics, which also retrieves content.

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?

Provides a workflow prerequisite ('obtain map_id from list_maps first'), which is useful sequencing guidance. However, it gives no when-to-use condition versus alternatives such as search_topics or alkemata-search-published-content for retrieving published content, leaving the choice implicit.

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