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

Annotations already declare readOnlyHint and idempotentHint, but the description adds meaningful behavioral context by specifying the metrics and time windows returned: tenders in the last 12 months, open now, median offers per award, single-offer share, award-sum quartiles, and frequent winners. It does not discuss pagination or response shape, but the metric list is substantive beyond the annotations.

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 definition is a single front-loaded sentence that states the scope first and then compactly lists the returned metrics. Every clause earns its place by clarifying either the aggregation level or the statistic produced.

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 does a good job listing the key metrics an agent will receive, and the required trade parameter plus optional geography are covered by the schema. A minor gap remains around the default behavior when land or kreis is omitted, but overall it is complete enough for correct invocation.

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 the schema already explains land, kreis, and gewerk, including examples and slug requirements. The description reinforces the geographic hierarchy and single-trade scope but adds no parameter-level detail beyond what the schema provides.

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 that this tool provides market statistics for one trade at Germany, Bundesland, or Kreis level, and it enumerates the specific metrics returned. It is distinguishable in practice from listing/search siblings because it is an aggregate analytics tool, though it does not explicitly differentiate itself by naming those siblings.

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?

Usage is implied: call this to get aggregate market figures for a trade in a geography. However, the description does not explicitly say when to use this instead of search_tenders or list_categories, nor does it state that gewerk must first be obtained from list_categories, even though the schema mentions that dependency.

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