create_invoice_payment

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

Annotations indicate a non-readonly write operation, but the description adds no behavioral details beyond 'create'. It does not disclose side effects, such as marking an invoice as paid, nor any prerequisites. With annotations present, the description contributes minimal additional transparency.

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 short, but under-specification is not conciseness. It omits necessary information and does not productively use its sentences.

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 5-parameter write tool with no output schema, a one-phrase description is completely inadequate. It leaves the agent unable to understand what the tool does, what inputs are needed, or what the expected result is.

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 schema documents 3 of 5 parameters, but 'date' and 'value' lack descriptions. The tool description does not explain any parameters, failing to compensate for the missing semantic coverage.

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 'Create payment' is a vague restatement of the tool name, omitting the invoice-specific context that distinguishes this tool from siblings like 'create_payment' and 'create_outgoing_payment'. It does not state that this creates a payment linked to an invoice.

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?

No guidance is provided on when to use this tool instead of alternatives. The description offers no context about scenarios, prerequisites, or relationships to other payment-related operations.

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