create_debit_card

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

No annotations provided, so description bears full burden. It discloses delivery modes but fails to mention side effects (e.g., cost, shipping time, card activation) or prerequisites (e.g., account must exist). The fallback parameter hint is not explained.

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?

Two sentences: first states purpose, second provides key usage hint. No filler, front-loaded with essential information.

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?

No output schema, so description could compensate by hinting at return value (e.g., card ID). It covers the main delivery distinction but omits details on error conditions, card limits, or activation steps. Adequate but not fully 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 coverage is 100%, so baseline is 3. Description adds meaning to order_status by clarifying usage for virtual vs. physical delivery. However, it does not elaborate on other parameters like product_type or monetary_account_id_fallback, which could benefit from additional context.

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?

Description clearly states 'Orders a new Mastercard debit card for a user,' specifying verb and resource. It distinguishes from sibling tools like create_credit_card by naming Mastercard debit, and provides specific delivery options.

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?

Description explicitly states when to use each order_status value (VIRTUAL_DELIVERY for immediate virtual, NEW_CARD_REQUEST_RECEIVED for physical). While it doesn't exclude alternatives like create_credit_card, the context of sibling tools makes the purpose clear.

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