create_bill_payment

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

There are no annotations, so the description must disclose behavioral traits itself. 'Create a bill payment' only conveys mutation; it says nothing about whether the bill's status changes, what side effects occur, required permissions, or error behavior. This is a significant gap for a write operation with zero annotation coverage.

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 short sentence with no wasted words, satisfying conciseness. It is under-specified, however, and mostly repeats the tool name, so it doesn't earn its place as a meaningful behavioral specification.

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 write tool with an opaque body parameter, no output schema, and no annotations, the one-line description is insufficient. The agent cannot know what fields body requires, what valid values look like, or what a successful response contains.

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 the single body parameter as a request body passed through to Bigcapital, but it doesn't describe any fields or constraints. The tool description adds no parameter-level meaning beyond the name, though the baseline is 3 due to high schema description 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 uses a clear verb ('Create') and resource ('bill payment'), making the basic operation obvious. However, it doesn't explain that bill payments settle vendor bills, leaving the distinction from sibling create_payment_received (customer payments) to be inferred from the tool name.

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 or when to choose a sibling such as create_payment_received, create_expense, or create_bill. The agent is left to infer context from the name alone.

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