accelo_get_invoice_line_item

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the '(Beta)' stability flag, which is useful, but says nothing about permissions, error behavior for invalid/missing IDs, or return shape for a lookup operation.

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?

Purpose is front-loaded in the first sentence and the Args block is functional with no filler. Appropriately sized for a two-parameter getter, though the parameter list format adds little polish.

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 with no output schema and only two parameters, the description is mostly sufficient. It is silent on failure modes (nonexistent ID, unauthorized access), which leaves a modest gap for an agent handling errors.

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 must compensate, and it does: both parameters are identified, and 'fields' is given concrete syntax ('line_item_ledger(),line_item_tax()') that appears nowhere in the schema. The 'id' explanation is essentially a restatement, which keeps this from a 5.

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 gives a specific verb and resource ('Get a single invoice line item by ID'), and the word 'single' implicitly separates it from the list/count siblings. It stops short of naming an alternative tool explicitly, so sibling differentiation is only implied.

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 use this tool versus accelo_list_invoice_line_items or accelo_count_invoice_line_items, and no preconditions (e.g., needing a known ID). Usage must be inferred from the name alone.

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