smokeball_list_bills

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

The description mentions routing under JWT/tenant/company scope but fails to disclose core behaviors like read-only nature, pagination, rate limits, or side effects. With no annotations, this is insufficient.

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 short with three sentences, avoiding unnecessary detail. However, the first sentence is redundant and could be omitted.

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 does not reference it or explain what the tool returns. It also lacks context about the domain (legal bills) and how to interpret results.

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 single 'arguments' parameter is described only as 'JSON string of arguments' with 0% schema coverage. The description does not explain the expected structure, keys, or provide examples, leaving the agent guessing.

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 it lists bills but provides no context on what bills are or how this differs from other similar list tools in the sibling set. The generic phrasing adds little beyond the tool 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 guidance on when to use this tool vs alternatives like clio_list_bills or billcom_list_bills. Also missing prerequisites, scope, or filtering info.

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