list_invoices

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

No annotations are provided, so the description carries the full burden. It only discloses the permission requirement. It does not mention pagination behavior, sorting, limits, or what happens if no invoices exist. For a listing tool, more transparency is expected.

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 sentence that efficiently conveys purpose and a key prerequisite. It is front-loaded and contains no unnecessary words. However, it could include additional context without becoming verbose.

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?

The tool is simple with an output schema, but the description lacks essential context such as pagination behavior, sorting, filtering, and common usage patterns. Given the absence of annotations and low schema coverage, the description is incomplete.

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 input schema has two parameters (page, limit) with defaults but no descriptions. The schema description coverage is 0%, and the tool description does not explain these parameters at all. The description adds no value beyond what the schema provides.

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 clearly states the verb 'list', the resource 'accounting invoices', and a specific permission requirement. It distinguishes itself from sibling tools like get_invoice (single invoice) and list_orders (different resource).

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 description mentions the required permission (Accounting), which is helpful for usage. However, it does not provide explicit guidance on when to use this tool versus alternatives like get_invoice, nor does it mention any conditions or prerequisites beyond permissions.

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