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

Annotations already disclose readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds meaningful behavioral context beyond annotations by clarifying that the 'Summe der offenen Posten' is reported as RESTBETRAG with partial payments already deducted. It does not mention auth or rate limits, but for a simple read-only overview with zero parameters this is not a significant gap.

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 two compact sentences. It front-loads the action ('Nennt die aktuellen Eckdaten'), lists the specific figures, uses a dash to clarify the RESTBETRAG nuance, and ends with a practical usage tip. Every sentence earns its place and there is no redundant content.

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 parameterless overview tool with no output schema, the description is remarkably complete. It specifies all included figures, interprets the meaning of one key metric, and provides guidance on when to call it. An agent can correctly invoke and interpret the result without additional documentation.

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?

There are zero parameters, so per the rubric the baseline is 4. The description does not need to explain any parameters; instead it focuses on output semantics, which is appropriate. No parameter-related information is missing.

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: 'Nennt die aktuellen Eckdaten' and enumerates the exact metrics (open orders, scheduled orders, unpaid/overdue invoices, sum of open items). It clearly distinguishes itself from search-oriented siblings like 'auftraege_suchen' and 'rechnungen_suchen' by offering a summary snapshot rather than a filtered list, reinforced by the phrase 'Guter erster Aufruf'.

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 gives a clear usage context: 'Guter erster Aufruf, um zu verstehen, worum es gerade geht' signals it is the initial orientation tool. It implies a 'when to use' scenario but does not explicitly name alternatives or state when not to use it (e.g., 'for detailed data use auftraege_suchen'). This is clear but not exhaustive.

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