list_job_invoices

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

The '[tier: readonly-owner]' tag conveys an access-level constraint, which is useful behavioral context beyond the schema. However, with no annotations provided, the description carries the transparency burden, and it does not state what happens if the job has no invoices (empty list vs. error), pagination behavior, or response ordering.

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 with zero waste: the first states the function and the second maps to the endpoint with an access-tier tag. Efficiently organized and front-loaded.

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?

This is a simple filtered-list tool with one parameter and no output schema. The description is reasonably complete for the simple use case, though it lacks detail on empty results, ordering, or pagination. The tier tag adds access context. Adequate but with room to describe return behavior.

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 carries full burden for the single parameter. However, job_id is a self-explanatory identifier and the description's 'for a specific job' clarifies its role as the job selector. With only one simple parameter, the baseline is acceptable even at 0% coverage.

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 clear verb+resource: 'List the invoices generated for a specific job.' It distinguishes from the sibling list_invoices (which lists all invoices) by specifying 'for a specific job.' The endpoint mapping adds precision. Not a 5 because it doesn't explicitly contrast with sibling list_invoices.

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 'for a specific job' phrasing implies the tool requires a job_id context, distinguishing it from a general invoice listing. However, there's no explicit when-to-use vs. alternatives guidance, no mention of list_invoices as the alternative for global access. Some implied usage context but no explicit exclusions.

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