freee_create_invoice

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

The description states 'Create a new invoice,' implying a mutation, but it does not disclose side effects (e.g., does it send notifications?), required permissions, or whether the invoice is created as draft or issued. With no annotations, the agent gets no behavioral safety cues.

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?

A single sentence 'Create a new invoice' is concise and immediately communicates the tool's purpose with no wasted words.

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?

No output schema exists, and the description does not mention return values, error conditions, or side effects. For a creation tool, the agent needs more context about what the response contains and what validates success.

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 coverage is 100% with clear descriptions for each parameter (e.g., 'Invoice status' enum). The tool description adds no additional meaning beyond the schema, so a baseline of 3 is appropriate.

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 a new invoice' clearly identifies the action (create) and the resource (invoice). It distinguishes this tool from read-focused siblings like freee_get_invoices and freee_summarize_invoices.

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 is provided on when to use this tool versus alternatives, no prerequisites (e.g., partner ID must exist), and no when-not-to-use conditions. The description is purely declarative with no context.

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