camelot_invoice_generator

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

Beyond the annotations, the description discloses important behavioral traits: local browser processing, unwatermarked PDF export, vector PDF output, and customizability. This is useful context beyond readOnly/destructive/idempotent hints and helps the agent understand privacy and output format expectations.

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 compact and front-loaded with the core purpose and key features. Minor issues include the redundant 'Invoice Generator Pro' label, a double-period typo, and the canonical URL, which adds little for an AI agent selecting or invoking the tool, but the overall structure remains efficient.

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 the 11-parameter schema with full coverage, annotations, and an output schema, the description covers the important context: it generates invoices, uses local processing, and exports unwatermarked PDFs. It does not explicitly address sibling tool distinctions or prerequisites, but nothing critical is missing for invoking the tool correctly.

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 100%, so the schema already documents all 11 parameters. The description adds conceptual context by mentioning 'editable line items, tax and discount fields,' which maps to items, taxPercent, and discountAmount, but it does not add syntax-level detail beyond what the schema provides.

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 states a specific verb and resource: 'Create customizable vector PDF invoices' with concrete features like multi-currency labels, line items, tax/discount fields, and local unwatermarked PDF export. It is clearly distinct from siblings such as purchase_order_generator or pay_statement by focusing on invoice creation.

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 intended use is implied: use this tool when the user wants to generate invoices as PDFs. However, there is no explicit guidance about when not to use it or which sibling alternative to choose instead, such as purchase_order_generator or statement_of_work.

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