list_creditors

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

With no annotations, the description must disclose behavioral details. It states a read operation ('abruft') but says it retrieves 'all' creditors while the schema supports limit/offset pagination. This is potentially misleading. It does not describe default limits, ordering, or whether results are paginated.

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 extremely concise, a single sentence in German with clear verb and resource. It is front-loaded and contains no fluff, making it efficient for quick parsing.

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's simplicity (3 params, all documented in schema, no annotations, no output schema), the description is adequate but not rich. It omits key behavioral context like pagination despite the limit/offset parameters, and the word 'alle' conflicts with the existence of limits. This could lead to agent misunderstanding.

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 coverage is 100%, so the baseline is 3. The description adds no value to parameter meaning; it does not mention limit, offset, or api_key, all of which are clearly described in the schema. The description is neutral and does not conflict with the schema.

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 clear, specific purpose: 'Ruft alle Kreditoren (Lieferanten) eines BuchhaltungsButler-Kontos ab' (retrieves all creditors/suppliers of a BuchhaltungsButler account). It clearly distinguishes itself from siblings like list_debtors (debtors) by naming the resource (creditors).

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 implies use when listing creditors but does not explicitly mention when to prefer this over alternatives or any exclusions. It lacks guidance on when not to use this tool (e.g., when filtering is needed or when using a different API key).

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