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

Annotations only declare readOnlyHint=true; the description goes beyond that by disclosing the return contract (an ordered JSON array of GeoJSON FeatureCollections, one per query) and the underlying endpoint. It omits other relevant behavior such as plan/quota restrictions for batch geocoding, which keeps it short of a 5.

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?

Three short sentences with the core capability front-loaded, followed by the return shape and endpoint. Nothing is padded or buried.

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 specifies the return structure, and the schema itself covers all parameters. Only error/partial-failure behavior and plan-gating for large batches are unaddressed, so it is nearly but not fully complete.

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%, so all seven parameters are already documented in the schema. The description only restates the 50-query ceiling and adds no syntax, format, or interaction detail (e.g. how types/country combine across the batch), matching the baseline 3.

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 and resource ('forward-geocode ... queries'), plus the distinguishing scope ('up to 50 queries in one request') that separates it from the single-query sibling maptiler_geocode. An agent can identify it as the batch variant without opening any schema.

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?

The batch framing implies when to use it (many queries at once), but the description never says so explicitly nor names maptiler_geocode as the alternative for single lookups. Usage is inferable rather than stated.

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