book_invoice

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

No annotations provided. Description only says 'mark it as paid' without disclosing side effects (e.g., invoice status change, authorization requirements, or whether it's destructive). An AI agent needs more behavioral context.

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, efficient sentence. However, it could be more structured with separate lines or bullet points for clarity, but it's not excessively long.

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 complexity (7 parameters, 5 required) and no output schema, the description is too minimal. It does not explain the booking process, return values, or what happens to the invoice after booking. Incomplete for an AI agent.

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 has 71% coverage (5 out of 7 parameters have descriptions). The description does not add extra meaning beyond the schema. Missing parameters like createFeed and checkAccountTransactionId are not explained, but the schema already covers most parameters, so baseline 3 is appropriate.

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?

Description clearly states the action: 'Book an invoice (mark it as paid)'. This distinguishes it from sibling tools like cancel_invoice or mark_invoice_as_sent, which have different purposes.

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 on when to use this tool vs alternatives, such as other invoice-related tools. No mention of prerequisites or typical use cases.

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