smokeball_create_bill

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

The description mentions routing and authentication scope but does not disclose behavioral traits such as whether the operation is destructive, idempotent, or what side effects occur. With no annotations provided, this leaves the agent with minimal behavioral understanding.

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 concise with three sentences, but its brevity comes at the cost of missing critical information. It is front-loaded with the operation name, but every sentence could provide more value.

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 is insufficient for a create operation. It does not explain what a bill is, what fields are required or optional, or what the output represents. The overall context is lacking.

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 description states that the 'arguments' parameter is a JSON string of arguments, which adds some meaning beyond the schema's type and default. However, with schema description coverage at 0%, this minimal information does not compensate for the lack of details on expected keys or structure.

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 identifies the tool as the Smokeball connector operation `create_bill`, including its platform name. However, it does not differentiate this tool from sibling Smokeball create tools (e.g., create_contact, create_matter), leaving ambiguity about what a 'bill' specifically entails.

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 is provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, intended scenarios, or situations where another tool would be more appropriate.

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