list_invoices

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

No annotations are present, so the description carries full burden. The short phrase does not disclose behavior such as pagination (cursor, limit), filtering parameters, or response format. For a list tool, key behavioral traits are missing.

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 very concise (one short phrase), which is efficient, but it omits essential details needed for correct tool usage. It is front-loaded but insufficiently informative.

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 complexity (6 optional parameters, no output schema, 15 sibling tools), the description is severely incomplete. It fails to explain filtering, pagination, or the result structure that the agent needs to use the tool effectively.

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 has 6 parameters with 0% description coverage, meaning no parameter descriptions exist. The tool description adds no information about what any parameter does, leaving the agent with only parameter names and types (and enum values) to infer usage.

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?

Description states 'List of invoices' which identifies the basic purpose, but lacks specificity to distinguish from sibling tools like list_unpaid_invoices or list_quotes. The verb 'list' is clear, but the resource scope is not elaborated.

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?

No guidance on when to use this tool versus alternatives such as list_unpaid_invoices or search_customers. The description does not provide context or exclusions.

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