wafeq_credit_notes_line_items_retrieve

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds the HTTP endpoint and resource scope, but no additional behavioral context beyond what annotations already provide.

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 with the key endpoint, but the final two sentences ('Retrieve credit note line item' and 'Endpoint for retrieving a single credit note line item') are redundant. It could be trimmed to one clear statement.

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-by-identifier endpoint, the description is functionally complete: it names the resource, gives the endpoint pattern, and annotations cover the safe/idempotent behavior. The absence of an output schema and low complexity reduce the need for deeper return-value documentation.

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 coverage is 0%, so the description carries the burden. The endpoint template shows that credit_note_id identifies the parent credit note and id identifies the line item, which adds relational meaning beyond bare schema. Still, it provides no further parameter detail or examples.

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 ('Retrieve') and resource ('credit note line item'), and reinforces it with the endpoint pattern. The word 'single' distinguishes this from list, create, update, and destroy siblings in the same credit-note line-item family.

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 is implied by 'retrieving a single credit note line item,' so an agent can infer this is for targeted reads rather than listing or modifying. However, it does not explicitly mention alternatives such as the line-items list endpoint or any exclusions/prerequisites.

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