tokportal_create_bundles_bulk

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

The description goes far beyond the annotations (readOnlyHint=false, etc.) by detailing atomicity, credit debiting, rolling capacity checks, contract_bundle_allowance, deterministic order, rollback behavior, and the handling of external_ref and idempotency_key. This provides rich behavioral insight that is essential for correct usage.

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 lengthy and contains detailed information that is valuable but not tightly structured. It is front-loaded with the main purpose, but the multiple paragraphs could be more concise. Some details, like advanced warming options, might be better placed in the schema or separate documentation.

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 description covers many aspects of the tool's behavior (atomicity, credit costs, advanced warming), but it does not describe the return value or response format. Given the complexity and absence of an output schema, this omission is a gap. Error handling is mentioned only briefly (rollback on failure).

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 100% schema description coverage, the baseline is 3. The description adds some extra meaning, such as the batch-level nature of external_ref and the idempotency_key usage, but most parameter details are already covered in the schema. The description does not significantly enhance parameter understanding beyond what the schema provides.

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 bundles in bulk. Creates and pays several bundles in one atomic creation checkout.' This is a specific verb (create) and resource (bundles in bulk), and it distinguishes from the sibling tool tokportal_create_bundle by emphasizing atomic bulk creation.

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 context for when to use the tool, including details about the atomic batch, credit consumption, and advanced warming options. It implies the tool is for multiple bundles, but does not explicitly state when not to use it or compare with alternatives like tokportal_create_bundle. The guidance is clear but could be more direct.

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