convert_estimate_to_invoice

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

With no annotations, the description carries the full behavioral burden for a mutation tool. It does not disclose what happens to the source estimate (deletion, status change), whether the operation is idempotent, what error occurs on a non-accepted estimate, or what the created invoice contains.

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?

A single front-loaded sentence with no filler that clearly leads with the action and target. It is efficient, though the terseness borders on under-specification for a stateful conversion operation.

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 mutation/creation tool with no annotations, no output schema, and an undocumented parameter, one sentence is insufficient. The agent still lacks the estimate's post-conversion fate, error conditions, and expected return, which are essential for correct invocation.

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 description coverage is 0% and the description adds no detail about estimateId beyond the implicit requirement that it reference an accepted estimate. It does not clarify format, valid ranges, or failure behavior for an invalid ID, so it fails to compensate for the undocumented parameter.

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?

States a specific verb (Convert) and the concrete resource transformation (accepted estimate → invoice), which lets an agent distinguish it from siblings like create_invoice. However, it does not explicitly name or contrast against create_invoice, so the differentiation is implied rather than 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 phrase 'accepted estimate' implies a prerequisite state, giving some guidance about when this tool is appropriate. But it never says when to use this versus create_invoice, nor what to do if the estimate is not yet accepted, leaving the selection logic implicit.

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