HALOWERK: Dienste auflisten

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

The description adds behavioral context beyond the annotations: it explicitly states 'Free — no wallet needed and no payment is made,' which is not covered by readOnlyHint=true. It also reveals that the tool returns a listing with specific fields. This is valuable contextual information that annotations don't provide.

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 three sentences, each earning its place: the first states the core purpose, the second clarifies cost-related behavior, and the third provides usage order guidance. It's front-loaded and free of filler.

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?

For a read-only listing tool with no output schema, the description provides adequate context: it lists the fields returned (price, hub, one-line summary), confirms it's free, and advises when to use it. It doesn't fully differentiate from sibling tools but covers the essentials for an agent to decide whether to invoke it.

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 input schema already provides detailed descriptions for all three parameters (hub, suche, hoechstpreis_usdc) with 100% coverage. The description does not add any additional parameter semantics, so the baseline of 3 is appropriate.

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 lists every HALOWERK service with price, hub, and one-line summary. It uses a specific verb and resource, and the phrase 'every HALOWERK service' gives scope. It doesn't explicitly distinguish from sibling tools like halowerk_preis, but the intent is clear.

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: 'Use this first to see what is available before spending anything.' This tells the agent when to use the tool (before making purchases) but doesn't name alternatives or explicitly state when not to use it. It gives clear context without exclusions.

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