billcom_create_bill

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

No annotations exist. The description adds routing info (JWT, tenant, company scope) but fails to disclose side effects, auth requirements beyond scope, rate limits, or that this is a write operation.

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?

Extremely brief but lacks substance. The routing info is front-loaded but the essential purpose and usage are missing. It is under-specified rather than concisely complete.

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 that the tool creates a bill (likely complex with many fields) and has an output schema, the description provides no information about return values, required arguments, or expected behavior. Severely incomplete.

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 'arguments' parameter is described only as 'JSON string of arguments' with no details on required keys, valid values, or format. Schema coverage is 0% and description does not compensate.

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 merely restates the operation name 'create_bill' without clarifying what a bill is or what creating it entails. It focuses on routing details rather than purpose.

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, when not to, or how it differs from sibling tools like billcom_approve_bill, billcom_list_bills, etc.

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