create_invoice

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

With no annotations provided, the description must carry full burden for behavioral disclosure. It only states 'Create' which implies mutation, but omits details on side effects, permissions, reversibility, or whether the invoice is automatically sent. This is insufficient 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 consists of two short, direct sentences without extraneous information. Every word is purposeful, making it highly concise and easy to parse.

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 (creation with two parameters, many siblings) and lack of annotations, the description misses crucial details about behavior, parameter semantics, and usage context. The presence of an output schema does not compensate for missing guidance on when and how to use 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 0%, so the description must compensate. It only notes that 'fields_json is a JSON object' without explaining the expected structure or detailing the project_id parameter. This adds limited value beyond the schema types.

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 action ('Create an invoice') and the target ('for a project'), providing a specific verb+resource combination. However, it does not differentiate from sibling tools like 'finalize_invoice' or 'approve_invoice', which could confuse an AI agent about which tool to use for particular invoice operations.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., project existence) or scenarios where this tool is inappropriate. No explicit when/when-not or sibling comparisons are provided.

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