fiken_create_purchase_from_draft

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds no extra behavioral details such as whether the draft is deleted after finalization, prerequisites like the draft existing, or side effects. It only restates the obvious write nature.

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 extremely concise (5 words) and front-loaded, but it could benefit from a bit more detail without being verbose. Still, it avoids unnecessary fluff.

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 lacks essential context: no mention of return value (the tool has no output schema), no prerequisites (draft must exist), and no behavior after creation (e.g., draft status). For a simple tool, this is incomplete.

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?

With 0% schema description coverage, the description should compensate but does not. The only parameter 'draftId' is implicitly referenced by 'from a draft', but no meaning is added beyond the schema's type and requirement.

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 'Creates a finalized purchase from a draft' has a specific verb and resource, clearly distinguishing it from siblings like fiken_create_purchase (creates from scratch) and fiken_create_purchase_draft (creates 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?

The description implicitly suggests using this tool when a purchase draft exists, but it lacks explicit guidance on when not to use it (e.g., if the draft is already finalized) or mentions alternatives like fiken_create_purchase.

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