List outgoing invoices

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

With no annotations, the description correctly identifies the tool as 'Read-only,' indicating idempotency and safety. However, it does not disclose pagination behavior, rate limits, or response structure beyond the listed fields.

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?

Single sentence plus 'Read-only' – extremely concise with no redundancy. Every word serves a purpose.

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 low-complexity list tool, the description covers purpose, returned data, and safety. Missing details about optional parameters and default limit are in schema; no output schema is needed. Adequate for its simplicity.

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?

Input schema has 100% description coverage (to, from, limit). The description adds value by listing returned fields (number, customer, sums, status, dates), helping users understand parameter context and output expectations.

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 'List invoices you issued' with specific fields (number, customer, sums, status, dates). It matches the title 'outgoing invoices' and distinguishes from invoice creation and PDF retrieval siblings, though not explicitly from other list tools.

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 implies read-only usage via 'Read-only' but does not explicitly state when to use this tool versus alternatives like sevdesk_create_invoice or sevdesk_get_invoice_pdf. No exclusions or context for other list operations.

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