dickerdata_get_invoice_details

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not mention response format, pagination, authentication requirements, or any constraints on the sales order / invoice relationship. This leaves important behavior undisclosed.

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 a single, front-loaded sentence with no filler or repetition. It is concise, though the brevity comes at the cost of parameter and usage guidance.

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?

Given the lack of output schema, annotations, and parameter descriptions, this minimal description is not enough for an agent to fully understand what the tool returns or how optional parameters behave. It identifies the core purpose but leaves important invocation details unspecified.

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%, and the description does not explain any of the three parameters. In particular, 'salesOrderNumberSuffix' and 'includeCustomerQualification' are not self-explanatory, and the description provides no compensating context. This is a significant gap for an agent trying to invoke the tool correctly.

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 ('Get') and resource ('line-item detail for a Dicker Data sales order / invoice'), so an agent can tell this is a detail-level retrieval tool. It does not explicitly contrast itself with siblings like dickerdata_get_order_details, but the line-item focus gives reasonable differentiation.

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 guidance on when to use this tool versus alternatives such as dickerdata_get_order_details, dickerdata_list_invoices, or dickerdata_get_order_serials. No exclusions or selection conditions are provided, so usage context must be inferred entirely from the tool name and terse description.

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