dnb_statistics_search

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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral details such as the need for an API key, the dataset parameter format, and the return structure (period, value, unit). No contradictions; adds value beyond 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 description consists of two concise sentences. The first covers purpose and examples, the second covers parameter usage and requirements. It is efficient but could be slightly more front-loaded with the most critical info.

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?

Given 5 parameters (1 required), existing annotations, and no output schema, the description covers purpose, key requirement, parameter format, and return structure. It points to DNB API documentation for more details. Missing explicit error handling or rate limits, but adequate for a data retrieval 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 description coverage is 80%. The description clarifies the dataset parameter format (pass as path or full URL), which adds slight value. Other parameters are adequately described in the schema, so the description provides minimal additional meaning.

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 it fetches datapoints from the DNB Statistics API, lists specific data types (interest rates, exchange rates, etc.), and specifies the return structure (period, value, unit). This differentiates it from sibling tools which are other Dutch government data APIs.

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 provides clear usage guidance: it mentions the required API key (DNB_API_KEY) and how to pass the dataset parameter. However, it does not explicitly contrast with alternatives or state when not to use this tool.

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