Merit Write Customers

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

The description clearly explains the preview-only nature: 'Does not execute changes; returns intended operation details and a confirmation_code.' This aligns with the readOnlyHint annotation and adds value by describing the confirmation flow. No contradiction.

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 informative but somewhat verbose and unstructured. It could be more concise and organized, e.g., bullet points for actions and payload fields. However, it is not excessively long.

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 9 parameters, no output schema, and a complex payload with many fields, the description lacks details on return values, payload structure, and all parameters. It covers only partial context, leaving gaps for effective tool selection and 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%. The description only lists some payload fields (Id, Name, CountryCode, etc.) but does not explain other parameters like filters, add_attachment, delivnote, bank_id, confirmation_code, or confirmed. This leaves many parameters undocumented.

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 preview-only write tool for creating/updating customers and vendors, with specific actions like customer_upsert, vendor_upsert, vendor_update. It distinguishes from sibling tools by focusing on customer/vendor writes and explicitly mentioning the confirmation step.

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?

Provides a typical use case: after receiving a purchase invoice, verify and sync vendor bank details. It also mentions the confirmation_code for merit_write_customers_confirm. However, it does not explicitly state when not to use it or alternative tools for other domains.

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