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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is handled. The description adds useful context such as the data source (Amt für Statistik Berlin-Brandenburg) and key response fields, which helps set expectations. However, it does not disclose behavior like pagination, limits, or the effect of the 'recent' parameter beyond the schema.

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 sections: summary, parameters, and key response fields. The core purpose is front-loaded. It is slightly redundant by saying 'at the Neighborhood level' while also allowing other rbs levels, and the parameter list formatting could be cleaner, but overall it is efficient.

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 tool has 10 optional parameters and no output schema, so the description carries a significant burden. It covers the main parameters and key response fields, which is adequate for basic use. Yet it leaves some parameter semantics underspecified (e.g., 'recent', 'include', 'fields' behavior) and contains the stadtteil inconsistency, creating completeness gaps.

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 high at 90%, so the baseline is 3. The description adds English translations for rbs enum values and explains geographic filter IDs, which is helpful. However, it lists 'stadtteil' and 'stadtteil_id' which are absent from the schema enum and properties, introducing ambiguity.

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 clearly states the tool provides 'Population stock for Berlin (headline figures)' at a specific geographic level (LOR Planungsraum), with a semi-annual cadence. This is a distinct resource from sibling tools like socio_berlin_age_groups or socio_berlin_origin, which focus on other dataset cuts. It lacks an explicit verb like 'returns' but the meaning is unambiguous.

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 gives the data scope and source but offers no guidance on when to choose this tool over alternatives such as socio_berlin_age_groups or berlin_neighborhood_search. It does not mention exclusions or conditions for using sibling tools. No explicit 'use X instead' direction is present.

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