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

With no annotations, the description carries the full behavioral burden, and it discloses only one trait: results are scoped to the calling API key. It says nothing about pagination, result limits, ordering, or whether the operation is read-only by implication, all of which matter for a list endpoint.

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?

A single short sentence that front-loads the action and resource with no filler or redundancy. Nothing in it is wasted, though its brevity is better characterized as under-specification in the completeness dimension than as a flaw here.

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 zero-parameter read tool with no output schema and no annotations, the description should at least indicate what comes back and whether results are paged or capped. It covers scope but leaves return shape and pagination entirely unaddressed, so an agent can call it but cannot predict its result set.

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?

The tool takes no parameters, so there are no argument semantics to explain and the baseline is 4. The description correctly avoids inventing parameters that the empty schema does not support.

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 (List) and resource (invoices) plus a scoping qualifier: only invoices created by this API key. That distinguishes it from a mutation sibling like create_invoice, but it never contrasts with check_invoice, which likely retrieves a single invoice, so an agent must infer the plural-vs-singular split.

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 only implied: an agent can reasonably infer this is the browse/enumerate-invoices tool, and the API-key scoping hints the results are limited to the caller's own records. There is no explicit statement of when to prefer it over check_invoice or when it is not appropriate.

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