Call Privat24 Business API

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Calls any business endpoint' and does not mention authentication requirements, potential side effects, rate limits, or error behavior. For a generic low-level call tool, this is a significant omission.

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 sentence with no fluff; the core action is front-loaded. It is concise and avoids verbosity, though it is so brief that it sacrifices substance in other dimensions.

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?

The tool is a low-level API caller with 4 parameters (including nested objects), no output schema, and no annotations. The description does not explain authentication prerequisites, endpoint discovery, request formatting, or any constraints beyond saying 'arbitrary.' It is incomplete for an agent to safely and correctly invoke this tool in all scenarios.

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 0%, so the description must compensate. It mentions 'arbitrary query parameters or JSON body,' giving a hint about query and body, but says nothing about the meaning of 'method' (get/post) or 'path', nor how query and body relate. The description fails to explain the structure or usage of any parameter in detail.

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 action ('Calls') and resource ('any business endpoint'), distinguishing it from the specific sibling tools (e.g., get_balances, create_payment) as a generic escape hatch. However, it does not specify what endpoints are available or how to discover them, so it is not fully self-contained.

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 'any business endpoint' implies this tool is for calls not covered by specialized siblings, but it never explicitly says 'use this when no sibling tool applies' or lists any alternatives. Guidance is implied rather than stated, leaving the agent to infer context from sibling names.

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