list_invoices

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

No annotations are provided, and the description fails to disclose behavioral traits such as pagination limits, default ordering, return count, side effects, or authentication requirements. The minimal description does not compensate for the lack of annotations.

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 extremely concise with two short sentences. The first sentence states the purpose, and the second provides guidance on a key parameter. No filler or redundancy, but it may be too sparse for adequate tool understanding.

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?

Given the tool's complexity (5 parameters, no required parameters, many sibling tools), the description is insufficient. It does not explain pagination, ordering, or differentiate from sibling tools. An output schema exists, so return values need not be described, but other context is missing.

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 should add meaning to parameters. It only mentions filter_expr for OData filtering, providing some semantic value. However, it does not explain top, skip, select, or orderby, leaving most parameters undocumented.

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 explicitly states the tool's action and resource: 'List invoices.' This is a clear verb+resource combination. Among many sibling list tools, this one is generic, but the purpose is clear.

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 provides limited guidance: 'Use filter_expr for OData filtering.' This tells when to use filter_expr but does not indicate when to use this tool versus other specialized list tools (e.g., list_finalized_invoices, list_paid_invoices). No exclusion criteria or alternatives are given.

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