beel_initiate_payment_connection

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

The description goes well beyond annotations, detailing the asynchronous authorization flow, the fact that the connection is created only after holder authorization, the activation requirement with specific error code, and the callback redirect behavior with error codes. It clarifies side effects (idempotency, non-appearance until authorization) and environmental handling (test/live), which annotations only hint at via flags.

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 longer than typical but every sentence carries useful information, covering purpose, flow, activation, and return details. It is well-structured with clear paragraphs, front-loading the core action before diving into conditions. While not terse, it is appropriately detailed for the complexity of the operation.

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 tool with no output schema, the description fully covers what an agent needs: the authorization flow, the returned authorization_url, the dependent parameters (return_url with appended statuses), the activation prerequisite with error handling, and idempotency nuances. It leaves no critical gaps 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?

Schema coverage is 67% and provides descriptions for company_id, body (provider and return_url), and idempotency_key. The description adds behavioral context about activation and error conditions but does not significantly enhance parameter semantics beyond what the schema already offers. It reiterates provider constraints but mainly repeats schema details, so it meets baseline without adding substantial new parameter-level meaning.

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's purpose: it opens an authorization session for a NIF holder to connect a payment provider and returns an authorization_url. It specifies the verb ('Opens an authorization session'), the resource (payment connection), and the action (returns the URL), and it distinguishes itself from related tools like beel_disconnect_payment_connection by focusing solely on initiation.

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 context on when to use this tool: when you need to connect a payment provider for a managed NIF. It explains the prerequisite (NIF activation) and the flow, and it implies the alternative (disconnect) is different, but it does not explicitly state 'when not to use' or name an alternative tool. Since no direct alternative exists among siblings, it's acceptable.

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