search_gas_consumption_public

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

With no annotations provided, the description discloses 'no auth required' and that it searches gas consumers, but it omits behavioral traits such as pagination, return format, or idempotency. It does not specify whether the tool is read-only or describe any side effects.

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 concise with three sentences: a bold statement of purpose, a short clarifying line, and a list of filter categories. It is front-loaded with key information and contains no unnecessary words.

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 the complexity of the tool (3 parameters, nested filters, no output schema), the description lacks information about what the search returns (e.g., fields of results), pagination details beyond what the schema provides, and usage boundaries. It covers the core purpose and filter categories but is not fully complete.

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 documents parameters thoroughly. The description adds some context by highlighting filter categories and giving examples, but it does not significantly augment the schema's parameter documentation.

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 searches for gas consumption units (Gasverbrauch) with 'Search' as the verb and specifies the resource as 'gas consumption units' (gas consumers). It distinguishes itself from siblings like search_power_consumption_public and search_gas_production_public by explicitly targeting gas consumption.

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 indicates the tool requires no authentication and is for finding registered gas consumers, which implies its appropriate context. However, it does not provide explicit when-to-use or when-not-to-use guidance or mention alternative tools.

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