Mark an invoice as sent

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

With no annotations, the description discloses that the tool changes data, honors dry run, refuses certain invoices, and verifies results. It does not cover authorization or rate limits, but the key behavioral traits are clear.

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 two sentences with a warning, all relevant. No wasted words; front-loaded with the main action and followed by important constraints.

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 no output schema, the description covers the action, refusal on enshrined invoices, dry run support, and verification. It lacks return value details but is sufficient for a mutation tool.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the sendType enum meanings ('PDF download, print, postal') and clarifying that email is excluded, going beyond the schema.

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 'mark as sent' and the resource 'invoice', and specifies the scope without emailing. It lists send types (PDF download, print, postal), distinctly differentiating from siblings like sevdesk_create_invoice or sevdesk_get_invoice_pdf.

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 that it refuses enshrined invoices and honors SEVDESK_DRY_RUN, providing context for when to use. It does not explicitly name alternatives but implies email-based sending is not included.

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