Convert estimate to invoice

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

Behavioral transparency is reasonably covered by annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true), which already indicate a state-changing operation. The description adds the detail that line items are carried over, which is helpful. However, it doesn't disclose any side effects on the estimate itself (e.g., whether it becomes void or marked as invoiced), nor does it mention any permission requirements or rate limits. Given annotations, this is acceptable but not rich.

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, concise sentence that leads with the action and key behavior. There is no extraneous text, making it efficient and easy to parse.

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?

The description is brief and leaves out important context. It doesn't specify the return value (new invoice), nor does it mention any prerequisites like the estimate must exist and be accepted. It also doesn't note the impact on the original estimate. With no output schema, this lack of information could leave the agent uncertain about the outcome.

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 50% – estimateId has no description in the schema, while locationId does have one. The description implicitly clarifies estimateId by mentioning 'estimate,' but it doesn't explicitly describe either parameter. It adds minimal value beyond the schema, so a score of 3 is appropriate given the moderate coverage.

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: creating an invoice from an accepted estimate, and notes that it carries over line items. This distinguishes it from ghl_create_invoice, which creates an invoice without an estimate, and from other estimate operations.

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 implies the use case (converting an accepted estimate) but does not explicitly state when not to use it or compare it to alternatives like ghl_create_invoice. It doesn't mention any preconditions beyond the estimate being accepted, and doesn't discuss cases where the estimate is not accepted or already converted.

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