create_split_payment

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Create a marketplace split payment' with no mention of side effects, idempotency, required permissions, or error behavior. For a mutation tool, this is a complete lack of transparency.

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 of six words, making it extremely concise. However, it is under-specified for the tool's complexity, containing no information about the split structure or marketplace context. It is not misleading, but it lacks the minimal detail needed to be truly helpful.

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 tool has 5 parameters including a nested 'splits' array, and there are no annotations or output schema to supplement the description. The one-sentence description does not explain what a marketplace split payment is, how splits relate to the total amount, or any constraints, leaving significant gaps for correct 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 coverage is 100%, so the baseline score is 3. The description itself adds no parameter details, but each parameter already has a minimal description in the schema. No extra semantic meaning is provided beyond what the schema already offers.

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 the action ('Create') and the specific resource ('marketplace split payment'), distinguishing it from sibling tools like 'create_payment' and 'create_pix_payment'. The addition of 'marketplace split' clarifies the unique purpose compared to a generic payment creator.

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 no guidance on when to use this tool versus alternatives such as 'create_payment' or 'create_pix_payment'. It does not mention any prerequisites, exclusions, or context that would help an agent decide between similar payment creation tools.

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