create_ap_invoice

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates that an AP invoice is created, but it does not disclose whether the invoice is posted, whether it validates the GRPO state, whether duplicates are prevented, what side effects occur in accounting, or whether the action is reversible. For a mutation tool, this is a significant gap.

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, front-loaded sentence that names the action, the source document, and the purpose in order of importance. Every phrase earns its place and there is no extraneous text.

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 moderate-complexity creation action with complete parameter schema coverage, but no output schema or annotations. The description gives enough to invoke it with grpoDocEntry, but it does not explain what the caller should expect in return, what happens if the GRPO is already fully invoiced, or any posting/approval behavior. Some of these gaps are acceptable for a simple creation tool, but at least one statement about side effects or output would make it more complete.

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 100%, so the baseline is 3; the schema already explains grpoDocEntry, docDate, and dueInDays. The description adds the conceptual link that grpoDocEntry refers to the source GRPO, which helps map the parameter to the workflow, but it does not add detail beyond the schema.

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 specific action ('Generate an A/P invoice'), the source resource ('Goods Receipt PO (GRPO)'), and the business purpose ('record the vendor payable'). This clearly differentiates it from siblings like create_ar_invoice, which is for customer receivables rather than vendor payables.

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 'from a Goods Receipt PO (GRPO)' clearly signals when this tool should be used: after a goods receipt exists and the vendor payable needs to be recorded. It implies the workflow stage and distinguishes it from earlier procurement steps like create_purchase_order or create_goods_receipt_po, though it does not explicitly name alternatives or exclusions.

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