wafeq_invoices_line_items_retrieve

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description confirms READ-ONLY/GET. It adds the endpoint path but no further behavioral detail such as response shape, error semantics, or authentication needs. For a simple retrieve with strong annotations this is acceptable but not additive.

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 a strong front-loaded summary of method, resource, and endpoint. However, 'Retrieve invoice line item' and 'Endpoint for retrieving a single invoice line item' are redundant restatements of the same idea, so one sentence does not earn its place.

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?

With only two required path parameters and annotation coverage for safety and idempotence, no output schema is needed to describe return values. The endpoint path makes the required parameters self-explanatory. The main gap is the absence of usage guidance, but the description is otherwise sufficient for a basic read-only retrieve.

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 input schema has only two string parameters with no descriptions (0% coverage). The endpoint line maps invoice_id to the invoice path segment and id to the line-item path segment, adding the hierarchy. It does not explain value formats, relationships to list operations, or where the IDs come from.

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 opens with a clear READ-ONLY marker and the exact endpoint GET /invoices/{invoice_id}/line-items/{id}/, then states 'Retrieve invoice line item' and 'Endpoint for retrieving a single invoice line item.' This identifies the specific verb, resource, and parent-child relationship, distinguishing it from the many sibling line-item retrieve endpoints by specifying invoice 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?

There is no statement of when to choose this tool instead of, e.g., wafeq_invoices_line_items_list or wafeq_invoices_line_items_update. The description only defines what the endpoint does, not the context, prerequisites, or alternatives. An agent must infer usage from the name and HTTP method.

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