penni_create_invoice

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

With no annotations provided, the description carries full burden for behavioral traits. It only notes that sending is optional and requires a subscription, but does not disclose side effects (e.g., what happens in QuickBooks), permissions, rate limits, or return values. This is insufficient for a mutation 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 a single 12-word sentence that efficiently conveys the core purpose and a key prerequisite. It is front-loaded with the action, but could benefit from slightly more structure without becoming verbose.

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 4 parameters (one optional boolean) and no output schema, the description leaves gaps: it does not explain what the tool returns after creation, how the 'send' option works in detail, or any error conditions. The agent lacks sufficient context to use it reliably.

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?

All 4 parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds no extra meaning or context beyond what the schema already provides, such as format hints or relationships between parameters.

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 and optionally send an invoice') and the resource ('through QuickBooks'). It distinguishes itself from sibling tools like penni_get_invoices (viewing) and penni_create_expense (expenses) by specifying the exact operation and target system.

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 mentions a prerequisite ('requires Penni subscription') but provides no explicit guidance on when to use this tool versus alternatives. It implies usage when an invoice needs to be created, but lacks exclusions or references to sibling tools for different tasks.

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