create_billing_item

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

With no annotations provided, the description carries the full burden. It only states that the tool creates a billing item, but fails to disclose side effects (e.g., creation is an insert, not an update), required permissions, or whether the operation is reversible. The mention of 'time entry or expense' is minimal 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 concise sentence with no fluff. Every word adds value given the space constraints.

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?

Despite having an output schema, the description fails to provide enough context for a complex 6-parameter tool. It does not explain parameter mapping for time entries vs expenses, nor does it cover usage scenarios or default behaviors, making it incomplete for effective tool invocation.

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 0%, so the description must compensate. However, it only mentions 'time entry or expense' without explaining how parameters like amount, rate, hours, or fields_json relate to these types. This adds negligible meaning beyond the parameter names.

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 the action (create) and resource (billing item), with a parenthetical specifying the types (time entry or expense). It distinguishes from sibling tools like get_billing_item, update_billing_item, and delete_billing_item which have different verbs.

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 description provides no guidance on when to use this tool versus alternatives (e.g., create_invoice), nor does it mention prerequisites, exclusions, or workflow context. This is a significant gap given the complexity of billing items.

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