unemployment

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

Description adds context about data granularity (per city per district) and source (Regionalstatistik) beyond annotations. Annotations already indicate readOnly, destructive false, idempotent, openWorld. No contradictions.

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?

Single sentence, no filler. Front-loaded with core purpose.

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?

Despite simple schema and annotations, the description lacks explanation of the slug parameter, output format, or data freshness. Incomplete for a tool with no param descriptions.

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?

The only parameter 'slug' has no description in schema (0% coverage) and the tool description does not explain its meaning. The user cannot know what slug represents, forcing reliance on external knowledge.

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 unemployment data (persons and rate) for a city per district, using specific verb 'Arbeitslose und Arbeitslosenquote' and resource 'Stadt je Kreis'. It distinguishes from sibling tools like demographics or indicators.

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?

No guidance on when to use this tool versus siblings like demographics or indicators. The description does not mention when-not or alternatives.

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