wafeq_quotes_line_items_list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description only repeats 'READ-ONLY' and adds an HTTP/path detail; it doesn't disclose pagination behavior, error cases, permissions, or response format. No contradiction with 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 first line is compact and informative, but the description contains redundancy: 'List quote line items' and 'Endpoint for retrieving a list of quote line items' say the same thing. The trailing restatement adds no new information.

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 straightforward read-only list operation, the necessary identifying information is present: resource, method, path, required quote_id, and pagination parameters. The lack of an output schema means the agent won't know the returned fields, but the description is otherwise adequate and annotations fill in the safety context.

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 endpoint pattern /quotes/{quote_id}/line-items/ reveals that quote_id is a path parameter, which is useful since the schema gives it no description. page and page_size are already described in the schema, so the description's added value is mainly for the required parameter.

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?

States a specific operation ('List') on a specific resource ('quote line items') and gives the endpoint path. The verb and resource make it distinguishable from the create/retrieve/update/destroy sibling tools for quote line items.

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 implies this tool is for retrieving all line items belonging to a quote, but it never states when to choose it over wafeq_quotes_line_items_retrieve, wafeq_invoices_line_items_list, or similar siblings. No exclusions or alternative routing are provided.

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