invoices_create_invoice_template

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

The description only says 'Create template', which implies a write operation consistent with readOnlyHint=false. However, it discloses no behavioral details such as whether this overwrites existing templates, what the response contains, or any side effects. The annotations provide basic safety info but the description adds nothing beyond the obvious.

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 a single two-word phrase, which is under-specified rather than concise. It lacks any structure or front-loading of key information. While brevity is generally good, this is so minimal it provides no value beyond the tool name itself.

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 tool's complexity (17 parameters, many nested objects, no output schema), this description is grossly inadequate. It does not mention required fields, what the template is used for, or any usage examples. An agent cannot confidently call this tool correctly without extensive external reference.

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?

The description provides zero parameter information. The schema covers 65% of parameters with descriptions, leaving several (e.g., currency, internal, termsNotes) undocumented. The description does not compensate for these gaps, forcing the agent to inspect the schema directly and puzzle over undefined fields.

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 'Create template' is extremely generic and fails to specify that this creates an invoice template specifically. It doesn't distinguish from sibling tools like invoices_create_estimate_template or invoices_create_invoice. The name provides some context, but the description adds no specificity beyond a bare verb and noun.

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?

There is no guidance on when to use this tool versus other invoice-related creation tools. No mention of prerequisites, common use cases, or alternatives. An agent receives no help in deciding between creating an invoice, an estimate, or a template of either type.

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