invoices_create_invoice_from_estimate

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

Annotations indicate readOnlyHint=false (write operation), destructiveHint=false, and idempotentHint=false, but the description adds no behavioral context beyond what the annotations already imply. It does not disclose side effects such as marking the estimate as invoiced (even though the markAsInvoiced parameter suggests this), nor any prerequisites like the estimate needing to exist. No contradiction with annotations, but the description is silent on behavior.

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 only one short phrase, which is concise but under-specified. It fails to front-load any useful details like intended use, prerequisites, or side effects. While there is no fluff, the brevity significantly reduces its usefulness; it is not informative enough to guide an agent.

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 tool that converts an estimate into an invoice, the description lacks critical context: what happens to the original estimate (e.g., is it automatically marked as invoiced?), requirements like the estimate existing, and any return value (no output schema is provided). The absence of these details makes the tool incomplete for correct invocation, even though the parameter list gives some hints.

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 input schema has 100% description coverage, so all parameters (estimateId, markAsInvoiced, altId, altType, version) are documented in the schema. The description adds no additional meaning about how these parameters relate to the operation. Per the rubric, baseline is 3 when schema coverage is high, and the description does not compensate or add value beyond the schema.

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 Invoice from Estimate" essentially restates the tool name (invoices_create_invoice_from_estimate) with slight rephrasing. It identifies the verb and resource but adds no detail that distinguishes it from other invoice tools like invoices_create_invoice or invoices_record_invoice. It is not a pure tautology, but it provides no extra clarity about the conversion process or conditions.

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 zero guidance on when to use this tool versus alternatives. It does not mention that it requires an existing estimate, how it interacts with the estimate's status (despite the markAsInvoiced parameter), or when to prefer this over other invoice creation methods. No exclusions or alternative tool references are given.

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