mark_invoice_as_sent

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

With no annotations, the description must disclose side effects. It only states the action without revealing if the invoice must be in a certain state, if the action is reversible, or if any email is sent. Insufficient detail for safe invocation.

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 (4 words), but at the cost of completeness. It is not verbose, but the brevity omits necessary context. Acceptable conciseness but insufficient information.

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 tool with 3 parameters, including an enum, and no annotations or output schema, the description is severely lacking. It should explain parameter effects and usage context to be minimally useful.

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 33%, yet the description adds no explanation for sendType (enum values VPR, VPDF, VM, VP) or sendDraft. The agent cannot deduce parameter meanings or correct usage from the description.

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 'Mark an invoice as sent' is clear about the verb and resource but does not differentiate from sibling tools like send_invoice_by_email, nor explain what 'mark as sent' entails (e.g., status update only vs. actual sending). It is adequate but lacks distinctiveness.

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 is provided on when to use this tool versus alternatives such as send_invoice_by_email, book_invoice, or cancel_invoice. The agent has no criteria to decide which tool to invoke.

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