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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a genuine constraint beyond them — data coverage is limited to the Netherlands — but says nothing about data source freshness, handling of coordinates outside coverage, or failure behavior for open-world lookups.

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-loaded purpose sentence followed by a scannable indicator list and an explicit Args block — easy for an agent to parse. The returned-field list partially duplicates the output schema, which is mild waste but aids tool selection.

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?

The output schema exists, so enumerating return fields is optional rather than necessary. The important gaps for a 2-parameter spatial lookup are geographic bounds and out-of-coverage behavior, neither of which is addressed; the description is adequate but not 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 coverage is 0% (only bare lat/lon titles), so the description must compensate; it does specify WGS84 and gives concrete example values for Rotterdam. However, it omits order sensitivity, valid ranges, and what happens with out-of-country coordinates, so the compensation is partial.

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 states a specific verb and resource: retrieve environmental and socioeconomic context for a Dutch location, and enumerates the returned indicators (buurt, municipality, density, green space, health, livability). That makes the tool's domain distinct from reading-oriented siblings such as get_latest_readings. It stops short of explicitly distinguishing itself from lookup_municipality, so a 4 rather than a 5.

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?

One contextual sentence gives implied timing: use it to understand local context before recommending BGI measures. There is no explicit when-not guidance, no prerequisites (e.g. must the location be inside the Netherlands?), and no named alternative for cases where only administrative lookup is needed.

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