Create Invoice

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

No annotations are provided, so the description must fully disclose behavior. It indicates a write operation ('Create') but does not describe side effects (e.g., marking the job as invoiced, irreversible changes), required permissions, or what happens upon success/failure. This is minimal transparency for a creation 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?

The description is two sentences long with no unnecessary words. It front-loads the core purpose and includes key details about line items. Every sentence contributes meaning.

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 5 parameters (including nested objects) and no output schema, the description is minimally complete. It covers the general purpose and line items but omits what the API returns (e.g., invoice ID), error handling, or prerequisites beyond 'completed job'. Adequate but leaves gaps for an agent to infer.

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 baseline is 3. The description adds value by explaining the line_items structure as an array of objects with name, quantity, rate, which reinforces the schema. However, it does not clarify other parameters beyond what the schema already provides. No significant additional meaning.

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 'Create', the resource 'Invoice', and the context 'in Zoho FSM for a completed job'. It also specifies the line items format, distinguishing it from siblings like create_estimate (different document type) and mark_invoice_paid (different action).

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 implies usage after a job is completed ('for a completed job'), providing a precondition. However, it lacks explicit guidance on when not to use this tool or mention of alternatives (e.g., creating an estimate instead). The context is clear but not comprehensive.

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