create_invoice_from_deal

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

Annotations indicate readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the agent knows this is a mutating, non-idempotent operation. The description adds valuable context by stating it 'automatically transfers deal information, products, and pricing', and the workflow clarifies that email sending and payment are separate subsequent steps. This goes beyond the bare mutation hints, though it does not mention failure modes or prerequisites.

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 exceptionally concise: one purpose sentence and one workflow line. Every word earns its place, with no repetition of schema details or filler. The front-loaded purpose immediately orients the reader, and the workflow adds unique context in minimal space.

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?

For a creation tool with 6 parameters and no output schema, the description covers the primary purpose, the automation behavior, and the intended downstream workflow. It does not explicitly describe return values or prerequisites beyond the required deal_id, but the schema covers the parameter, and the workflow makes the integration context clear. A small gap is lack of mention of what happens when send_email or include_line_items are toggled, but those are in schema.

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 6 parameters (deal_id, due_date, send_email, customer_id, invoice_date, include_line_items) already have descriptions in the schema, giving 100% coverage. The description itself adds little new parameter-specific meaning, but the workflow line ties the parameters to the overall process. Per guidelines, baseline 3 is appropriate when schema covers parameters fully.

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 opens with 'Create a Books invoice from a CRM deal', a specific verb+resource that clearly distinguishes it from generic invoice creation tools like books_create_invoice or books_convert_estimate_to_invoice. The title is descriptive and the workflow line reinforces the unique purpose.

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 workflow line 'CRM deal → Books invoice → books_send_invoice_email → books_create_payment' explicitly places this tool in a sequence, implying it should be used when starting from a CRM deal. While it does not explicitly name alternatives (e.g., books_create_invoice) or state when not to use it, the context is clear enough for an agent to infer the appropriate usage.

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