fiken_create_sale_from_draft

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

The description's 'creates' aligns with the readOnlyHint=false annotation, confirming a write operation. No additional behavioral traits (e.g., irreversibility, required permissions) are disclosed, but the annotation already covers the key safety implication.

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. It is front-loaded and free of superfluous text, though it could be slightly more informative without sacrificing brevity.

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?

Given no output schema and a single parameter, the description lacks details on the outcome (e.g., what the finalized sale object looks like), error conditions, or return value. This leaves the agent underinformed for proper 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?

The only parameter, draftId, has no description in the schema (0% coverage) and is not mentioned in the tool description. The description adds no meaning beyond the schema's type definition.

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 (creates) and resource (finalized sale from a draft), distinguishing it from related tools like fiken_list_sales or fiken_create_sale. However, it does not clarify what 'finalized' entails or the prerequisite of having a draft.

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?

No guidance is provided on when to use this tool versus alternatives such as fiken_create_sale or fiken_create_invoice_from_draft. There is no mention of prerequisites like the need for an existing draft.

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