get_requirementsGibt den empfohlenen Fragepfad für das Gespräch zurück sowie die verbindliche Liste von Feldern, die NIEMALS aktiv abgefragt oder weitergegeben werden dürfen (forbidden_fields).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| flow | Yes | ||
| forbidden_fields | Yes | ||
| allowed_prefill_fields | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only and non-destructive behavior; the description adds important contract details: forbidden_fields must NEVER be actively queried or passed on. This goes beyond the annotations and gives the agent a clear operational constraint.
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 a single compact sentence with no filler. It front-loads the main return value and immediately adds the critical forbidden_fields constraint without redundancy.
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 tool has no parameters, read-only annotations, and an existing output schema, the description provides sufficient context: it tells the agent what the tool returns and the key constraint around forbidden fields. Nothing essential is missing 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?
The tool has zero parameters and the schema coverage is 100%, so there are no parameter semantics to clarify. Per the zero-parameter baseline, the description appropriately focuses on what the tool returns rather than on inputs.
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 states a specific verb and resource: it returns the recommended question path for the conversation and the binding forbidden_fields list. This clearly differentiates it from siblings like quote or search_tariffs, which have no evident role in chat question routing.
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 phrase 'für das Gespräch' implies this tool is used to obtain chat guidance, and the mention of forbidden_fields suggests it should be consulted before collecting user input. However, there is no explicit statement about when to call it relative to siblings or what conditions exclude its use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a distinct step in the user journey: estimating consumption, retrieving requirements, looking up the network operator, quoting a tariff, searching/reading guides, listing tariffs, and starting a switch. Although search_flexenergy_ratgeber and read_flexenergy_ratgeber_article are related, their search-vs-read boundary is clear.
Most tools follow a clear verb_object snake_case pattern (estimate_consumption, search_tariffs, start_switch). The main deviation is 'quote', which lacks an explicit object and is somewhat ambiguous as verb vs noun; otherwise the naming is consistent.
Eight tools is well-scoped for a focused energy-advisory and switching assistant. Each tool supports a distinct part of the conversation without redundant utilities or excessive surface area.
The tool surface covers the full core flow: estimate usage, search tariffs, calculate a quote, provide switch link, plus supporting lookup and content-reading tools. There are no obvious dead ends or missing operations for the stated purpose.