zenoti-invoices-close

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

No annotations and description lacks disclosure of side effects (e.g., invoice becomes read-only, guest balance updated, receipt generated) or constraints (e.g., partial payments allowed). Simply states the action without behavioral context.

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?

Under-specification: only 4 words, which is too minimal to be useful. Conciseness should not sacrifice essential 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?

With no output schema, no annotations, and 4 poorly documented parameters, the description is severely incomplete. Lacks preconditions, side effects, and return values.

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 0% and description adds no parameter explanations (e.g., what invoice_id refers to, payment_amount unit, payment_type 'Custom' usage). Agent must infer from schema alone.

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 'Close invoice with payment' clearly specifies the verb 'close', the resource 'invoice', and the scope 'with payment', distinguishing it from sibling tools like 'zenoti-invoices-confirm' and 'zenoti-invoices-get'.

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, no prerequisites, no conditions (e.g., invoice must be open, payment amount must match balance).

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