Merit Write Purchases Confirm

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

Annotations already indicate destructiveHint=true (mutating) and readOnlyHint=false. The description adds that it is a 'confirmed mutating tool' and that it executes a write operation. However, it does not elaborate on the consequences or irreversibility, leaving some behavioral aspects ambiguous.

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 brief but contains redundancy (e.g., repeating 'Create purchase invoices') and could be streamlined. It front-loads the purpose but could be more organized.

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 has 9 parameters and no output schema or schema descriptions, the description is insufficient. It does not explain the full workflow (e.g., how to obtain confirmation_code from merit_write_purchases) or the meaning of many parameters, leaving the agent with significant 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?

With 0% schema description coverage, the description only explains 'action' (purchase_invoice_create) and mentions 'confirmation_code' and 'confirmed'. Six other parameters (id, filters, payload, add_attachment, delivnote, bank_id) are left undocumented, requiring the agent to infer or guess their purpose.

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 it is a confirm step for a previously previewed write operation from merit_write_purchases, requiring confirmation_code and confirmed=true. It also specifies the action 'purchase_invoice_create' to create purchase invoices. However, there is slight redundancy and the purpose could be more explicitly tied to the workflow.

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 specifies to use this tool when you have a confirmation_code and confirmed=true, implying it follows a preview from merit_write_purchases. It lists one supported action (purchase_invoice_create). It lacks explicit guidance on when not to use or alternatives, but the context is generally clear.

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