payments_create_integration_provider

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

Annotations already indicate this is a non-read-only, non-destructive operation. The description simply states 'Create', which aligns with annotations but adds no additional behavioral context such as uniqueness constraints, authentication requirements, or potential side effects. The description adds minimal value beyond the annotations.

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 short phrase—'Create White-label Integration Provider'—which is terse but not structured or elaborative. It lacks a complete sentence and offers no hierarchy of information, making it less helpful than a well-organized description that front-loads key details.

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 7 parameters, 5 required, and no output schema, the description is critically incomplete. It does not mention the return value, any constraints like uniqueName format, or the purpose of white-labeling. An agent would struggle to understand what 'white-label' implies without additional context.

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?

The schema provides 100% coverage with detailed descriptions for all seven parameters, so the baseline is 3. The description itself adds no parameter information, but the schema already carries the full burden, so no deduction is warranted.

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 verb 'Create' and the resource 'White-label Integration Provider', making the primary action unambiguous. However, it does not distinguish this tool from similar siblings like payments_create_integration, relying on the 'White-label' qualifier for differentiation.

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, no prerequisites, and no context about the intended use case. An agent receiving only this description would have no idea when to prefer it over other integration-provider creation tools.

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