card_update_options

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

No annotations are provided, so the description carries the full burden. It discloses that SCA may be required, describes polling and fallback, and mentions the sca_session_token for retry. It does not cover rate limits or detailed error handling, but the core behavioral traits are transparent.

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 with clear front-loading: first sentence states the purpose, second explains SCA behavior. No redundant information; every sentence earns its place.

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 SCA complexity and no output schema, the description explains the polling, fallback, and subsequent steps sufficiently. It lacks details on success/error response formats but covers the essential flow for an AI agent.

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%, baseline 3. The description adds value by explaining the SCA flow for the wait and sca_session_token parameters beyond the schema. The boolean options are simply listed, but the SCA-related context enhances parameter understanding.

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 explicitly states 'Update a card's options (ATM, NFC, online, foreign)', providing a specific verb and resource. It clearly distinguishes from sibling tools like card_update_limits and card_update_nickname.

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 explains SCA handling and polling behavior, including default wait time and fallback using sca_session_show + sca_session_token. It does not explicitly state non-SCA scenarios or alternatives, but the SCA guidance is clear and actionable.

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