wafeq_invoices_line_items_list

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

The annotations already establish that this is read-only, idempotent, and non-destructive. The description adds the HTTP method and endpoint path, but offers no additional behavioral detail such as pagination behavior, error cases, or response format. It does not contradict the annotations.

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 and front-loaded, but it is redundant: 'List invoice line items' and 'Endpoint for retrieving a list of invoice line items' say essentially the same thing. The endpoint path is useful, but the repeated sentence adds no 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?

For a simple read-only list operation with supportive annotations and pagination parameters in the schema, the description is mostly sufficient. However, there is no output schema and the description does not mention what fields the returned line items contain or how pagination behaves, leaving some uncertainty for the agent.

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 schema documents page and page_size, and the endpoint path makes it clear that invoice_id refers to the parent invoice. The description does not add detail beyond that, but with 67% schema coverage, the combination is adequate.

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 uses 'List' as the verb and identifies the resource as 'invoice line items' with the exact endpoint. It is unambiguous, though it relies on the resource name rather than explicitly distinguishing it from sibling line-item list tools for bills, purchase orders, quotes, etc.

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 alternative line-item list tools such as wafeq_bills_line_items_list or wafeq_purchase_orders_line_items_list. It simply states what the endpoint does without any context or exclusions.

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