create_ap_bill

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

The description adds 'Fails loudly', indicating that errors will be obvious, but no other behavioral traits are disclosed (e.g., permissions, idempotency, side effects). No annotations are present to compensate.

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 very short (two sentences) with no wasted words. It is front-loaded with purpose, but the version note '[Not in LCS /v1]' adds context. Could be more structured but is appropriately sized.

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 tool has one parameter, no annotations, and an output schema, the description should explain the parameter and expected usage. It does not, leaving the AI agent without sufficient context to use the tool correctly.

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 input schema has one required parameter (fields_json) with 0% schema description coverage, but the description does not explain what this parameter should contain or how to format it. It adds no value 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 clearly states 'Create an AP bill', which is a specific verb+resource. It distinguishes from siblings like update_ap_bill, delete_ap_bill, and other create tools (e.g., create_invoice) by the resource 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 usage guidelines are provided. There is no indication of when to use this tool versus alternatives like update_ap_bill or create_invoice.

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