ghl_estimate_convert_to_invoice

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds OAuth scopes and endpoint details but does not disclose whether the estimate is automatically marked as invoiced or other side effects.

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 repeats the purpose three times ('Creates a new invoice from an accepted/existing estimate', 'Create Invoice from Estimate', 'Create a new invoice from an existing estimate'), making it less concise. It is front-loaded but could be trimmed.

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 explains the core action and includes endpoint and OAuth scopes, but lacks details about return values, prerequisites (e.g., estimate must be accepted), and behavior of the 'markAsInvoiced' parameter. For a simple creation tool, it is somewhat complete but has gaps.

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 100% with descriptions for all parameters. The description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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 'Creates a new invoice from an accepted/existing estimate', which is a specific verb+resource. It distinguishes from sibling estimate and invoice tools by specifying the conversion action.

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 when to use this tool (converting an accepted/existing estimate to an invoice) but does not explicitly state when not to use or compare to alternatives like ghl_invoice_create.

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