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

Annotations only declare readOnlyHint=true, so the description carries the rest — and it does disclose the shape of the payload (unit price, cost, quantity, amount in cents), which is meaningful given there is no output schema. It omits pagination/result-limit behavior, keeping it short of a 5.

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?

Two sentences, front-loaded with the operation and payload, with zero filler. The trailing API endpoint note (GET /jobs/{job_id}/line_items) is marginally redundant but useful for tracing the underlying call.

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 one-parameter read tool with no output schema, the description supplies enough: scope, returned fields, and units. Only pagination/ordering behavior is absent, a minor gap for a simple list endpoint.

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?

With a single required parameter at 100% schema description coverage, the schema already documents job_id fully; the description only restates it as 'one job'. Baseline 3 is appropriate since there is little room to add meaning.

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?

States a specific verb (List) and resource (a job's line items) and enumerates what the items are (services, materials, labor, discounts) plus the fields returned. This clearly separates it from sibling reads such as housecall_list_job_invoices or housecall_get_job.

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?

The phrase 'on one job' implies the tool is used once you have a job_id, giving modest contextual guidance. However, it never names an alternative (e.g., get_job vs. this tool) or states when not to use it, leaving the agent to infer routing.

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