wafeq_bills_line_items_retrieve

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description's '🟢 READ-ONLY' marker just repeats the annotation, and it only adds the transport detail (GET endpoint path). 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 definition is short and front-loaded with the READ-ONLY marker and endpoint path, which is good. However, 'Retrieve bill line item' and 'Endpoint for retrieving a single bill line item' are near-duplicates that restate the same idea, wasting one of the three lines.

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 two-parameter read-only retrieve with rich annotations and no nested objects, the description is largely sufficient: it conveys the operation, the endpoint, and the read-only nature. The main gap is the absence of any return-value description given there is no output schema, but this is minor for a conventional single-resource 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?

Schema description coverage is 0%, so the description must compensate, and the URL template '/bills/{bill_id}/line-items/{id}/' does clarify the role of each parameter: bill_id scopes the parent bill and id identifies the specific line item. However, it does not explain ID formats, where to obtain them, or any constraints, leaving the agent partially informed.

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 a specific verb and resource ('Retrieve bill line item') and includes the HTTP method plus endpoint path, so an agent can clearly tell this is the single-item GET operation. The word 'single' differentiates it from the list sibling, but no sibling is explicitly named, so differentiation relies on RESTful convention rather than direct statement.

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?

Usage context is implied rather than stated: an agent can infer this tool is for fetching one bill line item when both bill_id and id are known, given the endpoint template. However, there is no explicit when-to-use guidance, no mention of how this differs from wafeq_bills_line_items_list, and no exclusions or alternatives are named.

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