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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context beyond that: polygon geometry is returned as GeoJSON URLs, lat/lon point lookups return only containing areas typically 0 or 1 match, extensions can be nested, and key response fields are disclosed. This is strong informative value for an agent.

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?

The description is well-structured with clear parameter sections, key response fields, and a use-case line. It is moderately long but every section carries necessary invocation information. Slight redundancy exists because parameters are repeated both in the description and the schema, but this is acceptable for clarity.

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?

For a five-parameter read-only filter tool without an output schema, the description covers selection criteria, parameter constraints, response shape, and concrete usage scenarios. Nothing crucial is missing for an agent to decide when and how to call this tool.

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 100%, so the schema already documents all five parameters. The description adds value by specifying that lat and lon must be provided together, explaining that include accepts 'centroid' with polygons provided as GeoJSON URLs, and clarifying erweiterungen embeds extensions as a nested array. This exceeds the baseline for fully covered schemas.

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 identifies the resource as Berlin social conservation areas with 124 areas in 6 categories, and states concrete use cases: point lookup for address checks and overview of all areas. It distinguishes itself from sibling tools like berlin_boroughs and berlin_neighborhoods by focusing on Milieuschutzgebiete, though it lacks an explicit imperative verb like 'list' or 'query'.

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 description explicitly states when to use the tool ('Use for: Is this address in a social conservation area? overview of all MilieuSchutz areas') and explains when lat/lon is appropriate. It does not, however, mention when to prefer sibling tools like berlin_conservation_area_details for single-area detail lookup, so exclusion guidance is incomplete.

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