fiken_update_purchase_draft

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

The description only states 'Updates a purchase draft' without disclosing behavioral traits like side effects, required permissions, or error states. Annotations indicate readOnlyHint=false, consistent with a mutation, but no additional context is given.

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 sentence, which is concise but under-specified for a tool with 12 parameters. It does not earn its place by providing necessary guidance, resulting in insufficient information density.

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 the tool's complexity (12 parameters, 4 required, no output schema), the description is severely incomplete. It fails to explain return values, parameter relationships, or typical usage, leaving agents with minimal actionable insight.

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 42% schema coverage, the description does not explain any parameters beyond the schema definitions. It adds no meaning or context for fields like 'kid', 'lines', or 'payments', leaving agents to rely solely on the input schema.

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 'Updates a purchase draft' clearly states the action and resource, but it lacks specificity regarding what aspects can be updated. It does not differentiate this tool from sibling tools like fiken_update_invoice_draft or fiken_update_credit_note_draft, as all share a similar pattern.

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_purchase_draft for new drafts or fiken_delete_purchase_draft for removal. There are no prerequisites or usage scenarios mentioned.

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