create_invoice

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Generates a professional PDF invoice' and 'Free tool,' which implies a creation operation without cost, but lacks details on permissions, rate limits, output format (beyond PDF), error handling, or whether it's idempotent. This is a significant gap for a mutation tool with zero annotation coverage.

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 appropriately sized and front-loaded: 'Generates a professional PDF invoice.' is the core purpose, and 'Free tool.' adds a useful note. Both sentences earn their place by providing essential information without waste, making it efficient and well-structured.

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 complexity (8 parameters, mutation operation), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't explain the return value (e.g., PDF file or link), error conditions, or parameter details, making it inadequate for an agent to reliably use this tool without additional context.

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 adds no meaning beyond the input schema, which has 0% description coverage for its 8 parameters. It doesn't explain what parameters like 'ownName', 'clientAddress', or 'items' represent, their formats (e.g., date formats for 'invoiceDate'), or how 'items' should be structured. With low schema coverage, the description fails to compensate, leaving parameters largely undocumented.

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 tool's purpose: 'Generates a professional PDF invoice.' It specifies the verb ('generates') and resource ('PDF invoice'), and distinguishes it from siblings like 'scan_invoice' or 'generate_quote'. However, it doesn't explicitly differentiate from 'generate_quote' beyond the invoice vs. quote distinction, which is implied but not stated.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'Free tool,' which might imply cost considerations, but doesn't specify contexts, prerequisites, or exclusions. For example, it doesn't clarify when to use 'create_invoice' over 'generate_quote' or 'scan_invoice', leaving the agent without explicit usage instructions.

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