insumer_create_merchant

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

No annotations were provided, so the description carries full burden. It discloses key behavioral traits: creation grants free credits, ownership by API key, and a limit of 10 merchants. This adds significant transparency beyond the input schema.

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 two short sentences, front-loaded with the core action. Every sentence adds value (create, credits, ownership, limit). No wasted words.

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?

There is no output schema, and the description does not explain the return value of the tool. For a creation action, expected output (e.g., the created merchant object) is missing. However, the description covers creation behavior adequately. Given the lack of output schema, the description is partially complete.

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 100%, meaning each parameter already has a description in the schema. The tool description does not add additional meaning or constraints for parameters beyond what the schema provides. Baseline 3 is appropriate.

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 'Create a new merchant', which is a specific verb+resource. It distinguishes from sibling tools like insumer_get_merchant or insumer_list_merchants by focusing on creation and adding unique context (free credits, ownership, limit).

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 provides usage guidance: 'Receives 100 free verification credits', 'The API key that creates the merchant owns it', and 'Max 10 merchants per API key'. This tells the agent when to use (e.g., when creating a new merchant and having capacity) and implies when not to (if already at 10). No explicit alternative is given, but context from siblings is available.

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