wafeq_bills_line_items_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safe read-only nature is covered. The description adds the endpoint pattern (GET) and the 'READ-ONLY' flag in text, but those mostly repeat annotation info. It doesn't add meaningful behavior beyond what annotations provide, such as pagination defaults or error conditions.

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 repeats 'List bill line items' three times (in the emoji header, the plain sentence, and the endpoint line) with the endpoint path adding little informational value. It is padded rather than concise, and the redundant phrasing costs tokens without adding agent-useful detail.

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?

For a simple read-only list tool with rich annotations, the core purpose is conveyed. However, missing guidance on pagination behavior, the meaning of bill_id, and how this relates to sibling line-item lists leaves the agent short. It doesn't explain ordering, default page size, or what counts as a bill line item.

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 page and page_size parameters already have descriptions in the schema (67% coverage). The description does not add any extra meaning to bill_id beyond its presence in the path. Since schema description coverage is high and the tool is simple, the description's silence on params is acceptable but not value-adding.

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 bill line items and includes the endpoint path, which is clear about the resource. However, it doesn't differentiate itself from sibling tools like wafeq_purchase_orders_line_items_list or wafeq_invoices_line_items_list beyond the name itself. There's also redundant repetition of 'List bill line items' across the title, emoji header, and endpoint description.

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. It doesn't mention that bill_id is required, how pagination works, or when to use wafeq_bills_line_items_retrieve instead for a single item. The context signals show many similar line-item list tools, but the description offers no routing or selection help.

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