zenoti-invoices-confirm

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

No annotations present, so description must disclose effects. It only says 'confirm' without explaining consequences (e.g., status change, irreversibility). Insufficient for a mutation tool.

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?

Extremely concise but under-specified. The single phrase 'Confirm an invoice' is too sparse to be useful.

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?

Fails to provide sufficient context for a tool with one parameter, no output schema, and no annotations. Does not clarify what happens after confirmation or return value.

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 0%, and description does not add any meaning to the invoice_id parameter beyond its name. No format, source, or example provided.

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 it confirms an invoice, which is a specific action. However, it lacks specificity on what 'confirm' means (e.g., finalize, approve) and doesn't differentiate from sibling 'zenoti-invoices-close'.

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 (e.g., zenoti-invoices-close, zenoti-invoices-get). No prerequisites or context provided.

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